If the services are specified to be at application scope, all calls to either will have to wait on the same monitor at the synchronized block.
Scott Nichol ----- Original Message ----- From: "Martin Gainty" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, July 09, 2002 3:32 PM Subject: Re: Constructor Deadlock > Adam: > > If individual calls from client fail then why would java Call have more success? > If possible could you provide > 1)Specific services you are executing on Server (are they registered) > 2)Specific client call to the server code > (in code) > danke, > > Martin > > > > > > >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: > >For additional commands, e-mail: > > > -------------------------------------------------------------------------- ------ > Chat with friends online, try MSN Messenger: Click Here > -- To unsubscribe, e-mail: For additional commands, e-mail: > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
