Adam, If you are using Application or Session scope for your services, this behavior is by design. Creation of an instance of a service object is synchronized on the app or session in those cases to ensure that only one instance is created per application or session.
Scott Nichol ----- Original Message ----- From: "Adam Moore" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, July 09, 2002 11:36 AM 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]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
