Hi,
I am using axis with websphere for my Java web application.I am using stubs generated by WSDL2Java tool by axis 1.4. In my application what happens is that one of the SOAP calls takes time to return (or probably never returns). Because this call is in synchronized java block, all the other threads keep waiting for this particular call to return and after some time the web application stops responding. The threads start piling up and finally the max threads limit is reached and the application crashes. ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 45" (5f813d2c) has been active for 772,317 milliseconds and may be hung. There are 50 threads in total in the server that may be hung Atleast the SOAP call should timeout after sometime. From axis website this property by default is 60 secs. I am not able to figure out the reason...why the soap call gets stuck up and never returns. Am I hitting some maximum SOAP call limit. Is there any configuration parameter that I can tweak to get rid of the problem? Is it that by manually overriding the timeout may solve the problem.. FooServiceLocator loc = new FooServiceLocator(); FooService binding = loc.getFooService(); org.apache.axis.client.Stub s = (Stub) binding; s.setTimeout(1000); // 1 second, in miliseconds Any inputs please advise.Or is this issue with the webservice server?? Thanks! Aditya
