MustGather: Read first for all Apache Geronimo Components

Technote (troubleshooting)


Problem(Abstract)

MustGather documents aid in problem determination and save time resolving Problem Management Records (PMRs).

Resolving the problem

Collecting MustGather data early, even before opening the PMR, helps IBM® Support quickly determine if:

  1. Symptoms match known problems (rediscovery).
  2. There is a non-defect problem that can be identified and resolved.
  3. There is a defect that identifies a workaround to reduce severity.
  4. Locating root cause can speed development of a code fix.


MustGather: Readme first table of contents:

Gathering general information Gathering general information
Submitting information to IBM Support Submitting information to IBM Support




Gathering general information:
  1. Copy the version of Apache Geronimo, as well as list of installed patches into a text file.


  2. Locate the InstallDir/var/log/server-log4j.properties file. Set the value of log4j.rootCategory to "DEBUG, CONSOLE, FILE".


  3. If you are experiencing a problem in a specific component, locate the related LOG4J categories in InstallDir/var/log/server-log4j.properties file, then set appropriate log level to generate output that shows where the problem occurs.

    Note: By default, all the categories have the "WARN" log level. Typically, changing the log level to "DEBUG" will provide useful information for problem determination.


  4. Restart the Application Server and recreate the problem.


  5. If there is a testcase application, deploy the testcase application on to the server and collect the expanded application folders in InstallDir/repository, after recreating the scenario.

    Note: There is no InstallDir/config-store/index.properties file in the version 1.1 of Apache Geronimo. When a J2EE™ application archive is deployed on to the server, the deployer will expand the archive into InstallDir/repository/groupId/artifactId/version folder and deploy it. The groupId, artifactId and version are the values of module configuration elements in geronimo plan of J2EE™ application archive.

    If there is no geronimo plan for the application, server generates a module configuration for the application and displays it on console during deployment. Locate the expanded folders for the application in InstallDir/repository using the module configuration values generated.


  6. Collect the following data:
    InstallDir/var/catalina/logs/*.log
    InstallDir/var/derby/*.log
    InstallDir/var/log/*.log
    InstallDir/var/log/*.properties
    InstallDir/var/txlog/*
    InstallDir/etc/*


  7. Bundle the above information. We suggest using zip or tar.


  8. If the problem being experienced is related to start-up of the server, set the appropriate log levels by following Steps 1 to 3 and restart the server to collect the logs mentioned in the Step 6. Finally, follow the link at the bottom of this technote to submit the collected logs to Support team.

Submitting information to IBM Support:
It is necessary to open a PMR before sending information to IBM Support. If a PMR is already open, update the PMR after sending information.

Follow directions for Submit diagnostic information to IBM Support.

Tip to save you time:
If you open and update your PMRs electronically, using ESR, update the PMR to indicate that data has been sent.

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Support for Apache Geronimo
General

Software version:

1.1, 1.1.1, 2.0.1

Operating system(s):

Linux, Solaris, Windows

Software edition:

Enhanced, Entry

Reference #:

1232407

Modified date:

2006-04-24

Translate my page

Machine Translation

Content navigation