I run into a similar problem when deploying a service using application scope. After reviewing the code, I think that the problem is in:
org.apache.soap.server.http.ServerHTTPUtils.getTargetObject
The scopeLock is obtained using the servlet context. I think it could be solved if we were to synchronize using the DeploymentDescriptor which is usnique per service (plus changing all the references inside the same method that use the context). I haven't had a change to try it out (for lack of time). But I think it should work.
--Emilio
-----Original Message-----
From: Adam Moore [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 09, 2002 5:36 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Constructor Deadlock
I have a class that implements a SOAP service. In the constructor of
that class, I want to make a SOAP call (using the Apache "Call" class)
to a different service that is running in the same JVM, and everything
hangs. Looking with jdb, it appears that the call is awaiting the
response from the doPost(), but the called service is never actually
invoked. Neither service can be called at this point from an external
client.
Environment:
Sun JDK 1.3.1
Tomcat 3.3.1
Apache SOAP 2.3.1
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
