Troubleshooting
Problem
You might need to collect data to resolve problems that you encounter when you use IBM® WebSphere® Application Server Liberty™ (Liberty).
Resolving The Problem
Requesting dumps for a Liberty server that is running with the IBM SDK:
System dumps are not available for HotSpot-based Java's (such as Eclipse® Temurin™, or Oracle® Java™) .
The dump type can be any combination of thread, heap, or system, specified by:
--include=thread
--include=heap
--include=system
--include=thread,system,heap (Or any combination)
|
- Run the dump command:
The location of the dump file is returned when the command completes.- For Windows® platforms, run:
<LIBERTY_HOME>\bin\server.bat dump <serverName> --include=<desired dump type> - For UNIX® platforms, run:
<LIBERTY_HOME>/bin/server dump <serverName> --include=<desired dump type>
- For Windows® platforms, run:
- Collect the resulting dump zip file.
The current Liberty dump command also gathers deployed applications.
- Guidelines for setting ulimits
- Crash on AIX® produces no core or a truncated core
- Steps 1 through 3 only.
- Crash on Linux® produces no core or truncated core
- Steps 1 through 3 only.
- MustGather: Crash on Windows
- Section Configuring Full Core Dumps.
There are two formats of trace output: text-based and binary. This document shows how to set up text-based tracing. If you are interested in setting up binary tracing, see the Configuring binary logging in Liberty topic in IBM Docs.
For text-based tracing, there are three formats: BASIC, ADVANCED, and ENHANCED. This document shows how to set up BASIC text-based tracing. See the Logging and Trace topic in IBM Docs to find more information about Liberty logging and trace.
The trace strings are specific to a module or component within WebSphere Liberty that you want to troubleshoot.
- Enable trace on the target Liberty server:
- Open the server.xml file in the root directory of the target server:
<LIBERTY_HOME>/usr/servers/<server>/server.xml
Where LIBERTY_HOME is the location of the extracted binary or is <AppServer>/wlp if Liberty is installed with WebSphere Application Server Version 8.5. - Add a <logging> element to the server.xml file.
- For example, to trace for the web container component with BASIC logging, add the following snippet to the server.xml file:
<logging traceSpecification="com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:HTTPDispatcher=all" traceFileName="trace.log" maxFileSize="20" maxFiles="10" traceFormat="BASIC" />
- For example, to trace for the web container component with BASIC logging, add the following snippet to the server.xml file:
- Open the server.xml file in the root directory of the target server:
- If possible, stop the server and clear the logs under the following directory:
<LIBERTY_HOME>/usr/servers/<serverName>/logs - Re-create the problem and collect the information.
- Follow the instructions on Exchanging information with IBM Technical Support for problem determination to send diagnostic information to IBM support.
Trace specifications available
If you cannot find a trace string for the feature that you want, check the MustGather: Read first for WebSphere Application Server and Liberty page to find a MustGather page for the feature.
The following trace strings can be used as the trace specification with the previous instructions to diagnose an issue in a specific component:
- Class loading
MustGather: Classloader problems for WebSphere Application Server Liberty Profile
Note: OSGi class loading issues require the use of the OSGi console. See the Using an OSGi console topic in IBM Docs. - Configuration
com.ibm.ws.config.*=all - Connections, Connection Pooling, and Transaction
RRA=all:WAS.j2c=all:com.ibm.ws.jdbc.*=all:Transaction=all:ConnLeakLogic=all - Deploy (EAR/WAR/EBA)
MustGather: Problems during deployment of EAR/JAR/WAR files in WebSphere Application Server Liberty - EJB
EJBContainer=all:Injection=all - Java Batch
com.ibm.jbatch.*=all:com.ibm.ws.jbatch.*=all - Java Management Extensions (JMX) or JMX client API (Server)
jmx.rest.server.connector=all:com.ibm.ws.jmx.connector.server.rest.*=all - Java Persistence API (JPA)
JPA=all - Java Transaction Service (JTS)
Transaction=all:com.ibm.ws.transaction.services.WebAppTransactionCollaboratorImpl=all - JavaServer Pages (JSP)
com.ibm.ws.jsp=all - JAX-RS (RESTful Web Services)
*=info:com.ibm.ws.jaxrs*=all:com.ibm.websphere.jaxrs*=all:org.apache.cxf.*=all:RESTfulWS=all:io.openliberty.org.jboss.*=all:io.openliberty.restfulWS.*=all:org.jboss.resteasy.*=all - JAX-WS (web services)
MustGather: JAX-WS/JAX-RPC Web Services engine problems for WebSphere Application Server
MustGather: Web Services Security (WS-Security) problems with WebSphere Application Server - JNDI and Naming
Naming=all:NamingService=all:org.apache.aries.jndi.*=all - JSF
com.ibm.ws.jsf*=all:org.apache.myfaces*=all:com.ibm.ws.webcontainer*=all:com.ibm.ws.jsp=all - Note: If you are using the faces-4.0 feature:
com.ibm.ws.jsf*=all:org.apache.myfaces*=all:com.ibm.ws.webcontainer*=all:io.openliberty.faces*=all
- Note: If you are using the faces-4.0 feature:
- Managed Executors and Thread Context Propagation
concurrent=all - If an issue with concurrency constraints (for example, max async or max queued:
concurrent=all:concurrencyPolicy=all - If an issue with context propagation to managed executor tasks:
concurrent=all:context=all - If an issue with the underlying thread pool:
concurrent=all:concurrencyPolicy=all:Threading=all
- If an issue with concurrency constraints (for example, max async or max queued:
- MQJMS
- If the IBM® MQ resource adapter uses either the wmqJmsClient-1.1 or wmqJmsClient-2.0 feature, enable the following trace:
*=info:JMSApi=all:Transaction=all:WAS.j2c=all:EJBContainer=all:Injection=all - If the IBM® MQ resource adapter uses generic JCA support, trace can be enabled by adding the following entry to the WebSphere Liberty jvm.options file:
A trace file called MQRA-WLP_<process identifier>.trc is written to the C:\Trace directory.-Dcom.ibm.msg.client.commonservices.trace.status=ON
-Dcom.ibm.msg.client.commonservices.trace.outputName=C:\Trace\MQRA-WLP_%PID%.trc
- If the IBM® MQ resource adapter uses either the wmqJmsClient-1.1 or wmqJmsClient-2.0 feature, enable the following trace:
- ORB
- For IIOP and Yoko ORB issues:
IIOP=all:org.apache.yoko.*=all:yoko.verbose.*=fine - For JNDI and Naming issues:
Naming=all:NamingService=all:org.apache.aries.jndi.*=all - CosNaming issues can involve both IIOP and JNDI, so enable both sets:
Naming=all:NamingService=all:IIOP=all:org.apache.yoko.*=all:yoko.verbose.*=fine
- For IIOP and Yoko ORB issues:
- Plug-in Generation
com.ibm.ws.webcontainer.osgi.mbeans.*=all - PMI/Performance Tools
- General:
com.ibm.websphere.monitor.*=all:com.ibm.ws.monitor.*=all:com.ibm.websphere.pmi.*=all:com.ibm.websphere.pmi.*=all:com.ibm.ws.monitors.*=all - In case the ConnectionPoolStats MBean is required, use the following trace string instead:
*=info:com.ibm.websphere.monitor.jmx.*=all:com.ibm.websphere.monitor.meters.Meter*=all:com.ibm.websphere.monitor.meters.Counter*=all:com.ibm.websphere.monitor.meters.Gauge*=all:com.ibm.websphere.monitor.meters.StatisticsMeter=all:com.ibm.websphere.monitor.meters.StatisticsReading=all:com.ibm.ws.monitor.*=all:com.ibm.websphere.pmi.*=all:com.ibm.ws.monitors.*=all
- General:
- Security
MustGather: Core security problems for WebSphere traditional and Liberty
MustGather: SSL problems on WebSphere Liberty
MustGather: Web SSO problems with WebSphere Application Server (OIDC, SAML, OAuth)
MustGather: SPNEGO problems on WebSphere Liberty
MustGather: Web Services Security (WS-Security) problems with WebSphere Application Server - Servlet Engine and Web Container
MustGather: Web container problems in WebSphere Application Server and WebSphere Liberty - Sessions and Session Management
com.ibm.ws.session.*=all:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all - For database persistence issues, add:
RRA=all - For trace scheduler problems, add:
persistentExecutor=all:concurrent=all:EJBContainer=all:RRA=all:WAS.j2c=all:com.ibm.ws.jdbc.*=all:Transaction=all
- For database persistence issues, add:
- SIBJMS
- SIB Connection problems
SIBTrm=all - SIB Communications and TCP/IP
SIBCommunications=all:SIBJFapChannel=all:TCPChannel=fine:com.ibm.io.async.*=all - SIB Client Applications
SIBJms*=all:SIBCommunications=all:SIBJFapChannel=all:SIBMessageTrace=all:SIBTrm=all:SIBJmsRa=all:SIBRa=all - SIB Locked messages
SIBProcessor=all:SIBMessageTrace=all - SIB MDB
SIBMessageTrace=all:SIBJmsRa=all:SIBRa=all - SIB Message format and schema
SIBMfp=all:SIBCommunications=all - SIB Message processor
SIBProcessor=all:SIBMessageTrace=all - SIB Message store
SIBMessageStore=all - SIB Performance
SIBMessageTrace=all - SIB Publish and Subscribe
SIBMatchSpace=all:SIBProcessor=all - SIB Security
SIBSecurity=all
- SIB Connection problems
- WebSocket
*=info:websockets=all:com.ibm.ws.webcontainer.*=all:com.ibm.wsspi.webcontainer.*=all:com.ibm.ws.webcontainer31.*=all:com.ibm.ws.servlet31.*=all:HTTPChannel=all:TCPChannel=all
Related Information
Was this topic helpful?
Document Information
Modified date:
10 August 2023
UID
swg21596714