wood burning stoves 2.0*
The moose likes BEA/Weblogic and the fly likes weblogic.utils.AssertionError Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "weblogic.utils.AssertionError" Watch "weblogic.utils.AssertionError" New topic
Author

weblogic.utils.AssertionError

Hari Jarinwallah
Greenhorn

Joined: Sep 19, 2011
Posts: 3
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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: weblogic.utils.AssertionError
 
Similar Threads
SOAP Exception : did not recognize the value of HTTP Header SOAPAction:
how to handle exception propagation in webservice client?
fault code
Calling .NET webservice from java client
WebService Error - Server side - while Response