Troubleshooting
Problem
Collecting data for problems with the IBM® WebSphere® Application Server JTS component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
Resolving The Problem
Tab navigation
- Learning more
- Troubleshooting
- Collecting data- selected tab,
Collecting data for problems with the IBM® WebSphere® Application Server JTS component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
MustGather: Read first for WebSphere Application Server
WebServices problem Classloader problem Dynamic Cache Problem JNDI Problem ORB Problem Scheduler Problem Session Management Problem Workload Management Problem
General Transaction trace specifications:
The below table shows a summary of the trace strings to use when gathering information for debugging Transaction problems.
Avoid trouble: If you are unfamiliar with how to enable WebSphere Application Server tracing, see the instructions here in Setting up a trace in WebSphere Application Server. NOTE: Enter the trace string as one complete line and allow it to wrap naturally so no hard breaks exist in the string.
Type of problem | Trace specifications |
| High level TransactionSummary Trace (TransactionSummary trace is added as a tool in 8.0.0.8 and 8.5.5.2) | *=info:TransactionSummary=all |
| General transaction Issues | *=info:Transaction=all:EJBContainer=all:WAS.j2c=all:RRA=all |
| Transactions with Web Services Atomic Transactions (WS-AT) is being used. | *=info:Transaction=all:EJBContainer=all:WAS.j2c=all:RRA=all:com.ibm.ws.webservices.trace.MessageTrace=all:com.ibm.ws.websvcs.trace.MessageTrace=all:WSCoor=all:WSTX=all |
| Transactions with ActivityService and ActivitySessions trace | *=info:Transaction=all:ActivityService=all:ActivitySession=all |
| Transactions with Compensation and Business Activity trace | *=info:Transaction=all:ActivityService=all:ActivitySession=all:CScope=all |
| Transactions with Compensation and Business Activity with Web Services Business Activity (WS-BA) is being used, | *=info:Transaction=all:ActivityService=all:ActivitySession=all:CScope=all:com.ibm.ws.webservices.trace.MessageTrace=all:com.ibm.ws.websvcs.trace.MessageTrace=all:WSBA=all:WSCoor=all |
| Transactions with Web Service Addressing trace | *=info:Transaction=all:com.ibm.ws.wsaddressing.*=all:com.ibm.ws.webservices.trace.MessageTrace=all:WSCoor=all:WSTX=all:com.ibm.ws.websvcs.trace.MessageTrace=all |
General questions:
For each JTS issue(s) we would need following information:
- Detailed description of the application topology.
- What are the symptoms noticed?
- Under what circumstances/scenario you see this problem?
- When did you see the problem first time?
- If it was working fine before what were the recent changes you made in this environment?
- How often does this problem occur?
- How do you recover from this problem?
- Is the resource (data source, J2C Connector, or a Message handling queue) starting the transaction a one-phase or two-phase (XA) commit?
- What is the application server's transaction timeout and transaction inactivity timeout?
- Are there any third-party Resource Managers involved (for example: Tuxedo, CICS® Transaction Manager, Unisys Transaction Manager)
Collecting basic mustgathers:
1. Provide a copy a snapshot of the configuration repository from the deployment manager profile using the collector tool. Run the collector tool located in the profile_home/bin directory on both Network Deployment (for federated environment only) and base Application Server profiles.
- Gathering information with the collector tool
If you are unable to provide collector jar then we would need the resources.xml files that contain the Application Server configuration of the resources involved in the transaction. These are in the following directory:
install_root\profiles\profile_name\config
The SystemErr.log and SystemOut.log files are located in the following directory:
install_root\profiles\profile_name\logs\server_name
The first-failure data capture (FFDC) logs are located in the following directory:
install_root\profiles\profile_name\logs\ffdc
If the problem appears related to the transaction service recovery logs, for example an error indicates that the logs are full, cannot be read successfully at server restart or recovery does not complete successfully, then providing a copy of the logs is recommended.
If you do not specify the transaction log directory during server configuration, the transaction service uses a default directory that is based on the installation directory: <profile_root>/tranlog/<cell_ name>/<node_ name>/<server_ name>/transaction. Above transaction directory contains 2 sub directories. 1) tranlog and 2) partnerlog. Both tranlog and partnerlog folders contains 2 files each. log1 and log2. Please tar the contents of these 2 directories: tranlog and partnerlog and send for review in addition to above requested logs.
Analyzing log files
After collecting the Application Server logs, identify the exceptions issued in the time frame surrounding the abnormal behavior. When looking through the exception stack (which reads bottom-up), you might encounter a transaction problem in which the last method called in the exception stack contains a class method with suffix com.ibm.ejs.jts.*. Some keywords and exceptions that can suggest a JTS problem:
- TransactionRolledBackException
- CSITransactionRolledbackException
- XAER_RMERR
- WTRN0006W: Transaction has timed out after nnn seconds
Advanced mustgathers/collecting Transactions trace:
Setting up a trace in WebSphere Application Server
1. Some times customers or IBM support team would like to know high level summary/information about transactions like start/end.commit/roolback calls information or to find out whether the transaction is long running or not, resources enlisted in a transaction, what component is initiating the transaction (application server or application itself) starts, commits or rolls back and performance of XA calls on particular resources. In this case following high level trace is enough.
*=info:TransactionSummary=all
Using TransactionSummary Trace in Websphere Application Server
2. In general, transactions (Transaction=all) trace on its own can often show there is a problem, but might not indicate the origin of the problem. The transactions trace is most useful when combined with EJB Container (EJBContainer=all) and Connection Manager (WAS.j2c=all) traces.
The following traces are required:
*=info:Transaction=all:EJBContainer=all:WAS.j2c=all:RRA=all
3. If Web Services Atomic Transactions (WS-AT) is being used, the following trace is required:
*=info:Transaction=all:EJBContainer=all:WAS.j2c=all:RRA=all:com.ibm.ws.webservices.trace.MessageTrace=all:
com.ibm.ws.websvcs.trace.MessageTrace=all:WSCoor=all:WSTX=all
NOTE: Enter the trace string as one complete line and allow it to wrap naturally so no hard break exists in the string.
4) Collecting ActivityService and ActivitySessions trace
The ActivityService is an underlying Unit of Work Service that is used by a growing number of components. Also, ActivitySessions provides a higher level of Unit of Work analysis than normal Transactions.
The following traces are required:
*=info:Transaction=all:ActivityService=all:ActivitySession=all
5) Collecting Compensation and Business Activity trace
The Compensation service provides a framework that allows business activities to be coordinated transactionally.
The following traces are required:
*=info:Transaction=all:ActivityService=all:ActivitySession=all:CScope=all
6) Transactions with Compensation and Business Activity and Web Services Business Activity (WS-BA) is being used, the following trace is required:
*=info:Transaction=all:ActivityService=all:ActivitySession=all:CScope=all:com.ibm.ws.webservices.trace.MessageTrace=all:
com.ibm.ws.websvcs.trace.MessageTrace=all:WSBA=all:WSCoor=all
NOTE: Enter the trace string as one complete line and allow it to wrap naturally so no hard break exists in the string.
7) Transactions with Web Service Addressing trace
Web Services Addressing (WS-Addressing) is a Worldwide Web Consortium (W3C) specification that aids interoperability between Web services by defining a standard way to address Web services and provide addressing information in messages
The following traces are required:
*=info:Transaction=all:com.ibm.ws.wsaddressing.*=all:com.ibm.ws.webservices.trace.MessageTrace=all:WSCoor=all:WSTX=all:
com.ibm.ws.websvcs.trace.MessageTrace=all
NOTE: Enter the trace string as one complete line and allow it to wrap naturally so no hard break exists in the string.
Follow instructions to send diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials specific to the JTS component, search the WebSphere Application Server support site.
Related information
Submitting information to IBM support
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server
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)
- FTP to the Enhanced Customer Data Repository (ECuRep)
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java Transaction Service (JTS)","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"},{"code":"PF035","label":"z\/OS"}],"Version":"9.0;8.5.5;8.5;8.0;7.0","Edition":"Base;Developer;Express;Feature Pack for CEA;Feature Pack for EJB 3.0;Feature Pack for SCA;Feature Pack for Web 2.0;Feature Pack for Web Services;Feature Pack for XML;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"}}]