ShowTable of Contents
Overview
At times, Lotus Expeditor Integrator may fail to receive or process JMS messages from various clients. This article provides a list of must-gather steps required for problem determination.
MQ JMS Trace
Begin by stopping the Integrator server. You may enable tracing either using the scripted or manual method. Once tracing has been update, start the Integrator server.
Scripted
On the command line change directory to the Integrator installation directory. Execute:
XPDintegMaint.bat -addParams maintenance\mqjmsON.txt
Trace files will be written to c:\temp by default. To change the location of trace files, edit the -DMQJMS_TRACE_DIR property in the mqjmsON.txt file. To disable tracing, execute:
XPDintegMaint.bat -addParams maintenance\mqjmsOFF.txt
Manual
Update the <rcp_data>\.config\rcpinstall.properties file with the following properties.
-DMQJMS_TRACE_LEVEL=base
-DMQJMS_TRACE_DIR=${rcp.data}/logs
Microbroker Trace Utility
More recent versions of Expeditor Integrator (6.2.1.20101101-2200) include a Microbroker trace utility.
Deploy the Trace Utility
If this is the first time you have enabled tracing, locate the directory <rcp_home>\tools, and unzip the XPDintegTools.zip into a same-named folder. The structure of the tools directory should now contain a new folder - for example, <rcp_home>\tools\XPDintegTools.
Configure the MBTrace.properties file prior to launching the batch file.
| Property | Description | Default Value |
| mbserverip | IP address of the server on which microbroker is running | localhost |
| mbserverport | Port on which the microbroker server is running | 1883 |
| userid | User name used to logon to the microbroker server | Admin |
| password | Password used to logon to the microbroker server | Admin |
| tracelevel | Microbroker trace level | TRACE_LEVEL_MAX
Additional values are:
TRACE_LEVEL_MIN, TRACE_LEVEL_LVL1, TRACE_LEVEL_LVL2, TRACE_LEVEL_LVL3, TRACE_LEVEL_LVL4, TRACE_LEVEL_LVL5 |
| tracelocation | Absolute or relative path where trace files should be stored | ../../persistent/microbroker/traces
The entire path (but the last folder name) should be pre-existing. The last folder would be created if not already present. If the last folder already exists, all files inside it will be deleted. |
| traceinterval | Time interval in milliseconds after which traces should be captures from the buffer | 900000; 15 minutes |
| tracecaptureduration | Duration for which the tool will continue to capture traces at regular intervals as specified by the traceinterval. The tool will exit on completion of this duration. | 172800000; 48 hours |
Launch the Microbroker Trace Utility
Start Integrator and subsequently execute the MBtrace.bat (or MBTrace.sh on UNIX) once the Integrator console appears. The batch file may be found in the <rcp_home>\tools\XPDintegTools directory.
After Problem Occurrence
Execute the following commands on the OSGI console.
The dump threads command should then be executed two more times. Ideally, execute the command thirty seconds after the previous command.
For more information on the OSGI console and its usage, see
An Overview of the OSGI Console.
Provide Data to IBM Support
- Create an ISA collection by using the OSGI commands referenced in IBM Lotus Expeditor Support Collecting ISA Data.
- Provide the ISA collection file referenced by the command output.
- Provide a ZIP file containing the following directories located within <rcp_home>, for example, D:\IBM\Lotus\Integrator:
- config
- flowdefs
- persistent