Troubleshooting
Problem
MustGather for problems with programming model extensions in WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Resolving The Problem
If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.
ActivitySessions
The ActivitySession service provides an alternative unit-of-work (UOW) scope to that provided by global transaction contexts. An ActivitySession context can be longer-lived than a global transaction context and can encapsulate global transactions.
To identify and resolve ActivitySession-related problems, you can use the standard WebSphere Application Server RAS facilities. If you encounter a problem that you think might be related to ActivitySessions, complete the following stages:
The ActivitySession service produces diagnostic messages prefixed by "WACS". The error message indicates the nature of the problem and provides some detail. The associated message information provides an explanation and any user actions to resolve the problem.
Check in the application server's SystemOut log at Install_Root/logs/server/SystemOut for error messages with the prefix WACS. If needed, check other messages, which should provide extra details about the problem.
See Troubleshooting ActivitySessions from Information Center for more information.
Application profiling
Application profiling enables you to identify particular units of work to the WebSphere Application Server run time environment. The run time can tailor its support to the exact requirements of that unit of work. Access intent is currently the only run time component that makes use of the application profiling functionality. For example, you can configure one transaction to load an entity bean with strong update locks and configure another transaction to load the same entity bean without locks.
See Application profiling exceptions from Information Center for more information.
Asynchronous beans
The asynchronous beans feature adds a new set of APIs that enable Java™ 2 Platform Enterprise Edition J2EE applications to run asynchronously inside an Integration Server. This topic provides a brief overview of the tasks involved in using asynchronous beans. For a more detailed description of the asynchronous beans model, review the conceptual topic Asynchronous beans. For detailed information on the programming model for supported asynchronous beans interfaces, see the topic Work managers
Dynamic caching
The dynamic cache service works within an application server Java virtual machine (JVM), intercepting calls to cacheable objects. For example, it intercepts calls through a servlet service method or a command execute method, and either stores the output of the object to the cache or serves the content of the object from the dynamic cache.
See Troubleshooting the dynamic cache service from Information Center
Dynamic query
Dynamic query service provides the ability to pass in and process EJB query language queries at run time, eliminating the need to hard-code required queries into deployment descriptors during application development.
Object pools
An object pool helps an application avoid creating new Java objects repeatedly. Most objects can be created once, used and then reused. An object pool supports the pooling of objects waiting to be reused. These object pools are not meant to be used for pooling JDBC connections or Java Message Service (JMS) connections and sessions. WebSphere Application Server provides specialized mechanisms for dealing with those types of objects. These object pools are intended for pooling application-defined objects or basic Developer Kit types.
To use an object pool, the product administrator must define an object pool manager using the administrative console. Multiple object pool managers can be created in an Application Server cell.
Trace String:
- ObjectPoolService=all=enabled
Scheduler
Schedulers are persistent and transactional timer services that run Enterprise Java Bean methods or send Java Message Service messages using any J2EE server application.
The scheduler service helps minimize IT costs and increase application speed and responsiveness by maximizing utilization of existing computing resources.
The scheduler service provides the ability to reliably process workloads using parallel processing and schedule resource-intensive tasks to process during low traffic off-hours.
See the MustGather: Scheduler problems for WebSphere Application Server
Startup beans
A startup bean is a session bean that is loaded when an application starts. Startup beans enable Java 2 Platform Enterprise Edition (J2EE) applications to run business logic automatically, whenever an application starts or stops normally.
Startup beans are especially useful when used with asynchronous bean features. For example, a startup bean might create an alarm object that uses the Java Message Service (JMS) to periodically publish heartbeat messages on a well-known topic. This enables clients or other server applications to determine whether the application is available.
See the MustGather: Startup Bean problems for WebSphere Application Server
Work areas
Work areas provide a capability much like that of global variables. They enable efficient sharing of information across a distributed application.
For example, you might want to add profile information as each customer enters your application. By placing this information in a work area, it is available throughout your application, eliminating the need to hand-code a solution or to read and write information to a database.
See the MustGather: Work Area problems for WebSphere Application Server
PMEs specific MustGather information:
- Collect the following:
- Provide SystemOut.log, SystemErr.log, trace.log, and ffdc logs
Files in install_root/profiles/profile_name/logs/server_name directory
FFDC logs from install_root/profiles/profile_name/logs/ffdc directory - What is the error or exception?
- Description of how the error or exception is generated or reproduced
- Detailed description of application topology
For a listing of all technotes, downloads, and educational materials specific to the PMEs, search the WebSphere Application Server support site.
Follow instructions to send diagnostic information to IBM support.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21199329