Troubleshooting tips

This reference information helps you prevent and recover from problems.

You can also search for troubleshooting tips by title or by using keywords.

Access intent troubleshooting tips
The following frequently asked questions involving access intent are answered.
Access problems after enabling security
Use this information if you are experiencing access problems after enabling security.
Application access problems
To resolve problems encountered when a servlet, JavaServer Pages file, stand-alone application or other client attempts to access an enterprise bean, ConnectionPool, or other named object hosted by WebSphere® Application Server, you must first verify that the target server can be accessed from the client.
Application client log error indicates missing JAR file
Application client SOAP request troubleshooting tips
Use this information to diagnose and troubleshoot problems with clients sending SOAP requests.
Application client troubleshooting tips
Debug common Java™ Platform, Enterprise Edition (Java EE) application client problems using this troubleshooting guide. Review the trace entries for one of the Java EE application client exceptions, and then locate the exception in the guide.
Application profiling exceptions
The following exceptions are thrown in response to various illegal actions related to application profiling.
Automation and recovery scenarios and guidelines
The following section provides information on how to monitor and recover WebSphere Application Server for z/OS® and the subsystems it uses.
Batch common problems
Occasionally, you might encounter behavior in the batch component that is not expected.
Bus-enabled web services: Known restrictions
There are a small number of known restrictions that apply when using service integration bus-enabled web services.
Bus-enabled web services troubleshooting tips
Use this set of specific tips to help you troubleshoot problems you experience with service integration bus-enabled web services.
Bus members troubleshooting tips
Use this set of specific tips to help you troubleshoot problems with bus members.
CEEDUMPs in the job log
An error caught by LE or the Java runtime can result in the production of a CEEDUMP, which is written to a separate CEEDUMP specification in the job log.
Choosing a Diagnostic Provider name
To ensure consistency when choosing Diagnostic Provider names to use with your components, you should consider the guidelines that follow.
CICS automation and recovery scenarios
This article explains different scenarios for CICS® automation and recovery.
Class loading exceptions
A class-loading exception error can help you determine the problem.
CORBA minor codes
Applications that use CORBA services generate minor codes to indicate the underlying cause of a failure. These codes are written to the exception stack. Look for "minor code" in the exception stack to locate these exceptions.
Data access problems
WebSphere Application Server diagnostic tools provide services to help troubleshoot database connection problems. Additionally, the IBM® website provides flexible searching capabilities for finding documented solutions to database-specific connection problems.
Data access problems for Apache Derby databases
Use troubleshooting tips for help accessing Apache Derby databases.
Data access problems for DB2 databases
This article provides troubleshooting tips for accessing DB2® databases.
Data access problems for Microsoft SQL Server data sources
Use troubleshooting tips for help accessing Microsoft SQL Server data sources.
Data access problems for Oracle data sources
Use troubleshooting tips for help accessing Oracle data sources.
Data access problems for Sybase data sources
This article provides troubleshooting tips for accessing Sybase data sources.
DB2 automation and recovery scenarios
This article provides scenarios for automation and recovery of DB2 resources.
Default messaging provider: Troubleshooting tips
Use this set of specific tips to help you troubleshoot problems for JMS messaging with the default messaging provider.
Diagnosing and fixing problems: Resources for learning
In addition to the documentation, there are several Web-based resources for researching and resolving problems related to the WebSphere Application Server.
Diagnosing batch problems using job logs
Occasionally, you might encounter behavior in the batch component that is not expected.
Diagnostic Provider Extensible Markup Language
Some conventions to follow for Diagnostic Provider (DP) Extensible Markup Language (XML) declarations.
Dump control settings
Use these settings to manage the dump control configuration in WebSphere Application Server.
Dump controls for IBM service
Use these controls to gather information that can be used by IBM service.
Troubleshooting tips for the dynamic cache service
The dynamic cache service works within an application server Java virtual machine (JVM), intercepting calls to cacheable objects.
Enterprise Identity Mapping troubleshooting tips
The following information provides troubleshooting information for Enterprise Identity Mapping (EIM) configuration or connection factory configuration.
Enterprise bean and EJB container troubleshooting tips
Enterprise bean cannot be accessed from a servlet, a JSP file, a stand-alone program, or another client
Use these troubleshooting tips for problems related to accessing enterprise beans.
Error Dump and Cleanup interface
The Error Dump and Cleanup (BBORLEXT) interface exists to call WebSphere Application Server for z/OS in a recovery environment to allow it to request a dump and to clean up its resources.
Error log stream record output
This article provides two samples of error log stream output and explains the various attributes they contain.
Errors configuring SSL encrypted access for security
You might have errors returned when you are trying to configure Secure Sockets Layer (SSL) for encrypted access. Some of the common errors you might encounter and suggestions on how to fix the problems are described.
Hexadecimal conversion of Java error codes
Occasionally, Java will take an WebSphere Application Server for z/OS error code (C9C2xxxx in hexadecimal) and convert it to a very large negative number. If you get a very large negative number, try converting it back to hexadecimal to find the correct code.
High availability environment troubleshooting tips
Review the following topics if you encounter a problem with your high availability environment.
HTTP session manager troubleshooting tips
Use troubleshooting tips for problems creating or using HTTP sessions with your web application hosted by WebSphere Application Server.
HTTP session problems
Use troubleshooting information for problems when creating or using Hypertext Transfer Protocol (HTTP) sessions.
IBM service call preparation
When you report a problem to IBM service, you will need to provide as much information as possible to help service personnel quickly resolve the problem.
IMS automation and recovery scenarios
This article provides scenarios for IMS automation and recovery.
Intelligent Management: application placement frequently asked questions
Occasionally, you might encounter application placement behavior that is not expected. This topic describes some commonly asked questions and things to look for when application placement is not working as you expect.
Intelligent Management: request prioritization problems
Occasionally, you might encounter flow prioritization behavior that is unexpected. You can look for some common things when request flow prioritization is not working as expected.
Intelligent Management: troubleshooting extended administration
Occasionally, when you are using the extended manageability features, you might encounter behavior that is not expected. For example, you can correct Web browser configurations so that your Web browser can support the visualization function.
Intelligent Management: troubleshooting health management
You can look for the following problems when health management is not working, or not working the way that you expect.
Interoperating with IBM MQ: Troubleshooting tips
Use this set of specific tips to help you troubleshoot problems when using the WebSphere MQ link or WebSphere MQ server components of the default messaging provider to interoperate with IBM MQ.
IPCS CTRACE subname query
If the trace data set is an SVC dump, the trace subname must also be specified. This subname is the aggregation of the address space's jobname with its ASID (address space identifier), in printable hexadecimal.
IPCS VERBEXIT subcommand to display diagnostic data
The interactive problem control system (IPCS) is a tool that provides formatting and analysis support for dumps and traces produced by WebSphere Application Server for z/OS and the applications that it hosts.
Logging Common Base Events in WebSphere Application Server
The following practices ensure consistent use of Common Base Events within your components, and between your components and WebSphere Application Server components.
Log output destinations and characteristics
Use these variables to control log output destinations and characteristics.
Logstream size considerations
You might need to modify the size of the logstream record size if the application server is attempting to write messages that are too large. If a message is too large, you will receive an error message that will be written to the job log.
Managing operator message routing
Use the product message routing capabilities to control server traffic flow.
Message location best practices
Use this information for configuring messaging locations.
Messaging engine troubleshooting tips
Use this set of specific tips to help you troubleshoot problems with service integration messaging engines.
Messaging troubleshooting tips
These tips are to help you troubleshoot your WebSphere messaging configuration.
Naming service troubleshooting tips
Naming is a Java Platform, Enterprise Edition (Java EE) service which publishes and provides access to resources such as connection pools, enterprise beans, and message listeners to client processes. If you have problems in accessing a resource which otherwise appears to be healthy, the naming service might be involved.
Object request broker component troubleshooting tips
The following topics might help you diagnose problems with the Object request broker (ORB) component.
Object request broker troubleshooting tips
Use these tips to diagnose problems related to the WebSphere Application Server Object Request Broker (ORB).
osgiCfgInit script
The Equinox OSGi framework is used to manage class loading and relationships between server component bundles. In some cases, the cached bundle data, which is maintained on a per-profile basis and has a separate cache at the WAS_HOME level for installation-wide processes, can become out of sync with the actual binaries on the server. You can use the osgiCfgInit script to clear and recreate the OSGi cache.
Password decoding troubleshooting tips for security
If the password encoding is corrupted and you cannot decode a password, you can complete one of the following tasks.
RACF automation and recovery scenarios
This table provides scenarios for RACF® automation and recovery.
RRS automation and recovery scenarios
Use this table for RRS automation and recovery scenarios.
Run-time environment: Best practices for maintaining the runtime environment
Use these guidelines to make sure that WebSphere Application Server for z/OS is customized and maintained correctly, to support your installation's application workload.
Scalable Vector Graphics problems
Consult this topic for problems and solutions for Scalable Vector Graphics.
Security authorization provider troubleshooting tips
This article describes the issues you might encounter using a Java Authorization Contract for Containers (JACC) authorization provider. Tivoli® Access Manager is bundled with WebSphere Application Server as an authorization provider. However, you also can plug in your own authorization provider.
Security components troubleshooting tips
This document explains basic resources and steps for diagnosing security-related issues in WebSphere Application Server.
Security configuration and enablement errors
Use this information to troubleshoot problems with configuring or enabling security.
Security enablement followed by errors
Use this information if you are experiencing errors after security is enabled.
Service integration bus security: Troubleshooting tips
Use this set of specific tips to help you troubleshoot problems you experience when working with a secure service integration bus.
Single sign-on configuration troubleshooting tips for security
Several common problems can occur when you configure single sign-on (SSO) between a WebSphere Application Server and a Domino® server. Some such problems are: Failure to save the Domino Web SSO configuration, authentication failures when accessing a protected resource, and SSO failures when accessing a protected resource. You can take some actions to correct these error situations and restore the SSO.
SPNEGO troubleshooting tips
You can securely negotiate and authenticate HTTP requests for secured resources in WebSphere Application Server by using the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO). You might encounter issues using Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) as the web authentication service for WebSphere Application Server.
SPNEGO trust association interceptor (TAI) troubleshooting tips (deprecated)
Presented here is a list of troubleshooting tips useful in diagnosing Simple and Protected GSS-API Negotiation (SPNEGO) TAI problems and exceptions.
Kerberos bind authentication troubleshooting tips
You might encounter issues when you use the Kerberos bind authentication with Generic Security Services API (GSSAPI) to connect the application server to an LDAP directory service. Tips and possible solutions are provided for issues such as a missing Kerberos principal name in a ticket cache file.
SSL errors for security
You might encounter various problems after configuring or enabling Secure Sockets Layer (SSL). You may not be able to stop the deployment manager after configuring the SSL. You may not be able to access resource using HTTPS. The client and the server may not be able to negotiate the proper level of security. The problems mentioned here are only a few of the possibilities. Solving these problems is imperative to the successful operation of WebSphere Application Server.
SVC dumps
A SVC dump is a core dump initiated by the operating system generally when a programming exception occurs. SVC dump processing stores data in dump data sets that you pre-allocate, or that the system allocates automatically as needed.
System controls: Best practices for using system controls
Use this information as the best way to configure system controls.
System performance when logging messages and trace data
Using message logging and trace data can affect system performance depending on your system configuration.
TCP/IP automation and recovery scenarios
This table provides automation and recovery scenarios for TCP/IP configurations.
Timeout properties summary
You can use timeout properties to control the amount of time you allow for various requests to complete. Some of these properties map to internal variable names. The internal variable names are provided here to aid you with debugging.
Tips for troubleshooting mediations
Use this set of specific tips to help you troubleshoot problems with mediations.
Trace controls for IBM Support
Use these settings to view or modify your trace settings.
Transaction troubleshooting tips
Use these tips to help you troubleshoot problems with the WebSphere Application Server transaction service.
Troubleshooting HTTP sessions
Troubleshooting Intelligent Management for web servers
You can troubleshoot issues with Intelligent Management for web servers using logging and tracing.
Troubleshooting workload management
Types of configuration variables
You can configure a variety of configuration variables to control the behavior of WebSphere Application Server for z/OS.
Universal Discovery, Description, and Integration, web service, and SOAP component troubleshooting tips
Use this information if you are having problems deploying or running applications that use WebSphere Application Server Web services, Universal Discovery, Description, and Integration (UDDI), or SOAP components.
UNIX System Services automation and recovery scenarios
This table provides automation and recovery scenarios for using UNIX System Services.
Web application deployment troubleshooting tips
Deployment of a web application is successful if you can access the application by typing a Uniform Resource Locator (URL) in a browser or if you can access the application by following a link. If you cannot access your application, follow these steps to eliminate some common errors that can occur during migration or deployment.
Web server (servlet) automation and recovery scenarios
This table provides scenarios for web server (or servlet) automation and recovery.
Web services authentication, authorization and secure transport troubleshooting tips
Web services are developed and implemented based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification. The are several troubleshooting authentication and authorization considerations when you are securing web services.
Web services client runtime troubleshooting tips
Use these tips to troubleshoot web services clients.
Web services command-line tools troubleshooting tips
Use these tips to troubleshoot WSDL2Java and Java2WSDL command-line tools that are used when you develop Java API for XML-based RPC (JAX-RPC) web services.
Web services compiled bindings troubleshooting tips
Use these tips to troubleshoot compiled bindings of Web services that are developed and implemented based on Java programming models.
Web services gateway troubleshooting tips
Use this set of specific tips to help you troubleshoot problems you experience when using the web services gateway.
Web Services Invocation Framework troubleshooting tips
A set of specific tips to help you troubleshoot problems you experience with the Web Services Invocation Framework (WSIF).
Web Services Security troubleshooting tips
To troubleshoot Web Services Security, review the configurations with assembly tools to match the client and server request and the response configurations.
Web services serialization and deserialization troubleshooting tips
Use these tips to troubleshoot problems that you can have when you perform serialization and deserialization in web services.
WebSphere Application Server for z/OS (Daemon) automation and recovery scenarios
This article provides some scenarios for automation and recovery of WebSphere Application Server for z/OS.
WLM automation and recovery scenarios
This table provides scenarios for automation and recovery of WLM enabled systems.
Workload management runtime exceptions
The product client can catch workload management runtime exceptions and implement strategies to handle the situation. For example, it can display an error message if no servers are available.
WSIF (Web Services Invocation Framework) messages
WebSphere system messages are logged from a variety of sources, including application server components and applications. Messages logged by application server components and associated IBM products start with a unique message identifier that indicates the component or application that issued the message. Here is a list of the WSIF runtime system messages, with details of what each message means.
WSIF - Known restrictions
The known restrictions that apply when using WSIF include restrictions on threading, on SOAP headers and unreferenced attachments, and on data type mappings.
WS-ReliableMessaging known restrictions
The main known restrictions that apply to the implementation of WS-ReliableMessaging in WebSphere Application Server.
WS-ReliableMessaging troubleshooting tips
Tips for troubleshooting your WS-ReliableMessaging configuration.