Hari Jarinwallah

Hi,

we have got following error while invoking a web service.

java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [***** ASSERTION FAILED *****[ Keep-Alive Timer cancelled ]] FaultActor [null] Detail [<detail>weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Keep-Alive Timer cancelled ] </detail>]; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: ***** ASSERTION FAILED *****[ Keep-Alive Timer cancelled ][message(SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [***** ASSERTION FAILED *****[ Keep-Alive Timer cancelled ]] FaultActor [null] Detail [<detail>weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Keep-Alive Timer cancelled ] </detail>]; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: ***** ASSERTION FAILED *****[ Keep-Alive Timer cancelled ])]


At the server end, the request was accepted successfully and processed like any other request. As far as the timing is concerned, which we thought to be culprit here, there are some weird finding. As soon as the request is fired, it's registered in the weblogic access log at server end. However, there's 15 second delay between this and the time when the first service log appears in application log file.

The whole request takes about 2 second, but it's after another 43 seconds that we got this error in calling system. It's a one-off error, which we have never seen before. Some reading tells me that weblogic was asked to something impossible and it gave up. Some other sources suggests that it might be due to some bug in weblogic. Any ideas about this one?

I am not even sure how to replicate it.

Thanks for the replies.

And yes, only asynchronous operation will do the trick for me. What I want is to trigger some processes and without waiting for them to complete, return the web service response to client.

I don't want to go for asynchronous web service as I want to avoid the serialization overhead. But, I wonder if we have any way of calling these web services locally. Also, Axis 1.4 - not sure if it supports asynchronous web service.

Hi all,

I've requirement to start some processing after receiving a request and validating the same. The return of the web service response needs to be sent immediately after kicking off the process and shouldn't wait for it to be finished.

One possible way to do this was using different threads. But, my application is deployed on weblogic and for web service, it's using axis 1.4 (old application). I've read that it's not a good idea to create our own threads when weblogic is managing the same.

I am sure that this is very regular scenario so can any one guide me about what should be the correct approach?

thanks a lot!
Hari