• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Container Time Out

 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have a CMT SLSB in WebSphere 5.x that calls a remote web service. If we call the remote service with an incorrect password (I'd call this a bug on their end) they never return. Then our bean hangs forever.

We can simulate this with a local web service mock tester by setting the configurable latency to three minutes. It is different in that it does eventually return something.

In the log we see the container report a timeout after the configured 120 seconds. This happens both with the remote service and the mock service. But nothing at all happens in the calling code. When the mock service returns after 3 minutes, the calling code catches and reports a transaction timeout exception. Because the remote service never returns we never see an exception and the client hangs forever waiting.

I expected the time out to cause an exception and blow away the whole call into the session bean after 2 minutes. Does the thread waiting on the web service somehow block the exception? Does any of this make sense?
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hmmmm, known bug: http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg1PQ72575
http://www-1.ibm.com/support/docview.wss?uid=swg27005042
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic