• Post Reply Bookmark Topic Watch Topic
  • New Topic

EJB intermittently does not respond, causing client EJB to timeout  RSS feed

 
H Pereira
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have two applications running on the same physical server with weblogic 6.1sp4. An EJB FPP running in "App Int" makes a call to an EJB HOD running in "App Dir". The ejbs are set up to use container managed transactions (Required), & both have the same JTA timeout of 120 sec.
Normally EJB HOD returns in a second or two. The bean has logging at multiple points in the code (including before any processing). However, sometimes the HOD does not respond, causing the FPP bean to timeout. When this happens, not a single entry is made in the log file. The "App Int" logs show an exception "weblogic.transaction.internal.TimedOutException: Transaction timed out after 124 seconds".

In order to debug the problem, the code in HOD bean was changed so that the same log entires are also sent to the console logs (using System.out.println). Also the transaction setting for HOD was changed to NotSupported, so that it would not take part in the transaction initiated by "App Int". However, when the problem occured again, there was still no logging, either in the log files or in the console logs. The same exception was shown in "App Int". There was no exception captured in the weblogic logs of "App Dir".

We are unable to simulate the situation in any other environment. Any ideas on what might be the cause and suggestions on any steps we can take to simulate/isolate the problem will be highly appreciated.
 
Roger Chung-Wee
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Could EJB HOD be waiting for a JDBC Connection to become available?
 
H Pereira
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Roger Chung-Wee:
Could EJB HOD be waiting for a JDBC Connection to become available?


The first line of code in EJB HOD is an SOP and the second is a log entry.
After that there is more code, along with logging. Database access is done via some other classes, but further down in the code.

Even if the ejb were to be waiting for a JDBC connection, at least the SOP & logging should have been visible.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!