IBM Support

MustGather: EJB container problems with WebSphere Application Server

Troubleshooting


Problem

Collecting data 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. These instructions can be followed from a clean start or during a runtime session. Traces can be gathered during either.

Resolving The Problem

Tab navigation

Collecting data for problems with the IBM® WebSphere® Application Server enterprise java beans (EJBs). Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Collecting data manually


The following additional documentation must be provided when submitting EJB Container PMRs:
  • For all WebSphere Application Server releases:
    1. Enable the following trace:

      *=info:EJBContainer=all:PMGR=all:Injection=all

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

    2. Run the collector and upload that to IBM support using the instructions below.

Static trace:
  1. Log on to the administrative console.

  2. In left panel expand Troubleshooting. Click on Logs and Trace.

  3. Select the application server to be traced, and then on the next page click the Diagnostic Trace link.

  4. Select the Configuration tab.

  5. Select the Enable Log property (This checkbox is not present in V7 and later releases).

  6. Under Trace Output, select File radio button and specify File Name.
    • Also Increase the Maximum file size to 100 MB
    • Increase the Maximum number of historical files to 10.

  7. Select Basic (Compatible) Trace Output Format unless otherwise specified by support.

  8. On same panel click on Change Log Detail Levels under Additional Properties on right side panel.

  9. Under Configuration tab specify Trace Specification by entering the trace string specific to the MustGather documentation for which you are collecting data.

  10. Click Apply and OK. Then Save your configuration (select Synchronize changes with Nodes option).


Dynamic trace:
  1. Log on to the administrative console.

  2. In the left panel, expand Troubleshooting and click on Logs and Trace.

  3. Select the application server to be traced, and than on the next page click the Diagnostic Trace link.

  4. Select the Runtime tab (Server should be up and running for this tab to show up).

  5. Under Trace Output, select File and type a File name (if you do not specify path, but just the file name, then the default location of the file is under the application server profile directory).
    • Set the Maximum File size to 100Mb and
    • Set the Maximum Number of historical files to 10.

      Important:       Do not select Save Runtime Changes to Configuration as well if you do not want this setting to become permanent.

  6. On same panel click on Change Log Detail Levels under Additional Properties on right side panel.

  7. Select the Runtime tab.

  8. Under Trace Specification, enter trace string for the specific MustGather for which you are collecting data.

  9. Click Apply and OK. Then Save your configuration (select Synchronize changes with Nodes option).

Related information

Exchanging data with IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:

  • IBM Support Assistant (ISA)
  • Service Request (SR)
  • E-mail
  • FTP to the Enhanced Customer Data Repository (ECuRep)

Instructions for exchanging information with IBM Support

Read first and related MustGathers

MustGather: Read first for WebSphere Application Server

Web Services Security Problem Servlet engine and Web container problem Web services engine and tooling problem

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"EJB Container","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21244478

Page Feedback