MustGather: EJB container problems with WebSphere Application Server
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with the IBM® WebSphere® Application Server Enterprise JavaBeans™ (EJB) container. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem

1. Learning more 2. Troubleshooting 3. Collecting data

If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for WebSphere Application Server products
EJB container specific MustGather information
The following additional documentation must be provided when submitting EJB Container PMRs:
  • For releases of WebSphere Application Server V6.1 with EJB 3.0 Feature Pack.
  • Collect the files located in the following directory:

    install_root/profiles/profile_name/logs/server_name

  • Collect the FFDC logs located in the following directory:

    install_root/profiles/profile_name/logs/ffdc

  • Collect the following trace:

    *=info:EJBContainer=all:PMGR=all:JPA=all:openjpa=all

    Note: See Appendix A for steps on enabling the trace.

  • For releases of WebSphere Application Server V6.0:
    • Does the application use the EJB 1.1 or EJB 2.x specification?

    • Collect the files located in the following directory:

      install_root/profiles/profile_name/logs/server_name

    • Collect the FFDC logs located in the following directory:

      install_root/profiles/profile_name/logs/ffdc

    • Collect the following trace:

      *=info:EJBContainer=all:PMGR=all

      Note: See Appendix A for steps on enabling the trace.

  • For releases of WebSphere Application Server V5.0 and V5.1:
    • Collect the files located in the following directory:

      install_root/logs/server

    • Collect the FFDC logs located in the following directory:

      install_root/logs

    • Collect the following trace:

      EJBContainer=all=enabled:PMGR=all=enabled

      Note: See Appendix A for steps on enabling the trace.


Appendix A: Enabling EJB traces
The following will step you through enabling an EJB trace. This is only required on the application server, not on the deployment manager or node agent:
  1. Start WebSphere Application Server.

  2. Open the administrative console.

  3. Expand Servers > Application Servers > server_name.

  4. Select Diagnostic Trace Service.

  5. Add the trace string to the Trace Specification field.

    For example:

    EJBContainer=all=enabled:PMGR=all=enabled

  6. Click Apply and Save.

  7. Recreate the problem.

  8. Clear the trace string in the Trace Specification field:

    *=all=disabled
 
Related information
Running the collector tool
Submitting diagnostic information to IBM
Steps to get support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting Guide for WebSphere Application Server
MustGather: Persistence Manager
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > EJB Container
Operating system(s): z/OS
Software version: 6.1
Software edition:
Reference #: 1244478
IBM Group: Software Group
Modified date: Nov 30, 2007