Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creation of Burlap proxy hangs (together with the whole Tomcat) [SPR-3445] #8128

Closed
spring-issuemaster opened this issue May 2, 2007 · 6 comments

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented May 2, 2007

Oleksandr Alesinskyy opened SPR-3445 and commented

I have created a small demo application for Spring remoting capabilities. It iterates over configured proxies and calls remote service over each of them (the same way as JPetStore sample application does, but unlike to JPetStore client is Web-based).

Client context (see attached Zip) contains proxies for Hessian, Burlap and HttpInvoker. The problem is that application context creation hangs on creation of Burlap proxy (namely, in afterPropertiesSet()). Not only context creation hangs, but Tomcat stops to respond, even for appication that are already running (e.g. Tomcat welcome page, http://localhost:8080). See hang.log in the attached Zip. As soon as Burlap proxy is commented out application successfully starts and works properly.

To make things even more interesting, above mentioned behavior manifests itself only on Tomcat startup, if application is deployed in already running Tomcat, it works perfectly (till next Tomcat restart), see already_running_tomcat.log in attached zip.

Regards,
Oleksandr Alesinskyy


Affects: 2.0.3

Attachments:

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 2, 2007

Oleksandr Alesinskyy commented

Logfiles, client context definition (Burlap is commented out), service interface to be proxied

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 2, 2007

Juergen Hoeller commented

Where exactly does the initialization of the BurlapProxyFactoryBean hang - I suppose it's within the actual Burlap client initialization? In that case, I'm not sure that there is anything we can do about this in Spring itself, since it's Caucho's Burlap client library responsible there, with us just calling into it...

Juergen

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 8, 2007

Oleksandr Alesinskyy commented

This I can not say it hangs somewhere in the following code

    public void afterPropertiesSet() {
            super.afterPropertiesSet();
            prepare();
    }

    /**
     * Initialize the Burlap proxy for this interceptor.
     * @throws RemoteLookupFailureException if the service URL is invalid
     */
    public void prepare() throws RemoteLookupFailureException {
            try {
                    this.burlapProxy = createBurlapProxy(this.proxyFactory);
            }
            catch (MalformedURLException ex) {
                    throw new RemoteLookupFailureException("Service URL [" + getServiceUrl() + "] is invalid", ex);
            }
    }

Is it inthe Spring code or Caucho code I can not say.

Regards,
Oleksandr

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 11, 2007

Juergen Hoeller commented

This does mean that it's the Caucho BurlapProxyFactory hanging there, since all that the createBurlapProxy method does is a straight "proxyFactory.create" call on the BurlapProxyFactory...

Juergen

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 14, 2007

Oleksandr Alesinskyy commented

Then if I would write small tests that creates this proxy manually and would see if its hang, then post results here.

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Sep 27, 2007

Juergen Hoeller commented

Seems there's nothing that we can do about this in any case, since this is up to Burlap's implementation...

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.