TroubleShooting: EJB Container problems

Resolving The Problem

Steps to help resolve EJB problems

Before beginning the troubleshooting process, it might be helpful to review the educational material, tutorials, and demonstrations concerning EJBs and other WebSphere Application Server functionality that is available in the IBM Education Assistant.

A good starting point for troubleshooting is the documents available provided by looking up troubleshooting EJBs: starting point for troubleshooting EJBs. In the previous link, go down through the listing and pick the area that best suits your needs.

JNDI Problems
Are you experiencing a problem doing a JNDI lookup of an EJB?

• Yes, review this TroubleShooting document for JNDI Naming problems.



• No, continue to the next question.
  

Does a NameNotFoundException occur when the JNDI lookup of the EJB is done?

• Yes, review this technote.
  
  
• No, continue to the next question.
  
  

CORBA Problems
Does a CORBA error occur when your EJB client application tries to access the EJB?

• Yes, review this TroubleShooting document for Object Request Broker (ORB) problems.
• Special note! If you are receiving a CORBA.NO_IMPLEMENT No Cluster Data Available, with WLMLSDRouter.select() on the stack. This type of error is most likely a WLM issue. Check for a Work Load Management (WLM) issue by doing the following

 If there are multiple core groups, make sure they are bridged. First of all, make sure the core group is bridged and then verify the HA manager is enabled for all members in your cell. Also, verify all cluster members are part of a stable HA view. There is a special cluster called the LSD Cluster which the Node Agents use to get overall cell cluster information.   If the core groups are not bridged then the LSD won't contain information about all the nodes and clusters.  This is an example stack trace:

[9/8/13 6:29:10:337 EDT] FFDC Exception:org.omg.CORBA.NO_IMPLEMENT SourceId:com.ibm.ws.naming.jndicos.CNContextImpl.doLookup ProbeId:1838 Reporter:java.lang.Class@6dd66dd6

org.omg.CORBA.NO_IMPLEMENT:
>> SERVER (id=11c328fe, host=bsgplvwsp11) TRACE START:
>> org.omg.CORBA.NO_IMPLEMENT: No Cluster Data Available vmcid: 0x49421000 minor code: 42 completed: No
>> at com.ibm.ws.cluster.router.selection.WLMLSDRouter.select(WLMLSDRouter.java:295)
>> at com.ibm.ws.cluster.propagation.ServerClusterContextListenerImpl.forwardRequest(ServerClusterContextListenerImpl.java:625)
>> at com.ibm.ws.cluster.propagation.ServerClusterContextListenerImpl.validateRequest(ServerClusterContextListenerImpl.java:669)
>> at com.ibm.ws.wlm.server.WLMServerRequestInterceptor.notifyValidationListeners(WLMServerRequestInterceptor.java:317)
>> at com.ibm.ws.wlm.server.WLMServerRequestInterceptor.receive_request_service_contexts(WLMServerRequestInterceptor.java:206)
>> at com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorManager.java:621) ' 

No, continue to the next question.

Transaction Problems
Is the problem related to transactions?

• Yes, review the TroubleShooting documents for Transaction problems and continue to the next question. Transaction TroubleShooting documents.
  
• No, continue to question 1 under Database Connection and Connection Pooling Problems.
  
  

Is the problem related to a transaction timeout (WTRN0006W warnings appear in the SystemOut.log file)?

• Yes, consider changing the Total transaction lifetime timeout setting either globally or for a particular EJB.
  
  
• No, continue to the next question.
  
  

Database Connection and Connection Pooling Problems
Is the problem related to database connectivity or connection pooling?

• Yes, review the TroubleShooting document for Connection Pooling problems. TroubleShooting data access problems.
• No, continue to next question.
  
  

Web Services Problems
Does a java.net.SocketTimeoutException: Read timed out occur when trying to invoke a Web service from an EJB?

• Yes, Refer to Transaction Service Settings in the WebSphere Application Server Information Center for details on the transaction settings and how to increase the Application Server transaction time-out to allow the web service to respond.
  
  
• No, continue to the next question.
  
  

Review the WebSphere Application Server v7.0, v8.0, v8.5.5, or v9.0 Product Documentation, or the WebSphere Application Server support site for additional information that might help you to resolve the problem.


What to do next
If the preceding troubleshooting steps did not solve your problem, see the MustGather for EJB Container problems to continue investigation.