WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Troubleshooting asynchronous beans

This section provides some debugging tips for resolving common asynchronous beans problems. What kind of problem are you having?

Asynchronous Beans WorkEvents contain unreliable information

Explanation Information reported in the Asynchronous Beans WorkEvent object is incorrect and changes unpredictably. For example:
  • A WorkEvent for a unit of work that completes successfully might report that the unit of work failed with an exception.
  • A WorkEvent for a unit of work that never starts might report that the unit of work completed successfully.
  • A WorkEvent might report that the unit of work completed successfully, then at a later time report that the work did not start, and later report that the work failed while running, and so on.
Possible causes WebSphere Application Server pools and reuses WorkEvent objects that the application might still be using. WorkEvents are put into a pool after the WorkListener method completes. However, applications can continue accessing these WorkEvents outside the WorkListener method. This pooling and reuse results in values changing unpredictably in WorkEvents still in use by the application.
Recommended response A workaround for this problem is to access asynchronous beans WorkEvent objects only within the WorkListener method in which the WorkEvents are originally supplied. If the information in the WorkEvent is needed outside the WorkListener method, the application can copy the information contained in the WorkEvent to another object, and then access the new object outside of the WorkListener method. A fix will eventually be provided for WebSphere Application Server releases prior to V6.0.2. Use the workaround until a fix is available. If you use WebSphere Application Server v6.0.2, use this workaround permanently.

WorkItem result and exception are missing within the Asynchronous Beans WorkListener.workCompleted interface

Explanation When a WorkItem is accessed from the asynchronous beans WorkListener.workCompleted method, the WorkItem result and WorkItem exception are absent. A missing WorkItem exception might cause a failed unit of work to appear to the application as though it completed successfully.
Possible causes WebSphere Application Server is incorrectly waiting until after the WorkListener.workCompleted method completes to populate the WorkItem with the result and exception.
Recommended response If you use WebSphere Application Server V6.0.2, avoid accessing the WorkItem result from within WorkListener.workCompleted. If you use WebSphere Application Server releases prior to V6.0.2, search for any solution containing a fix for PK06636.

For current information available from IBM Support on known problems and their resolution, see the IBM customer support page.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM customer support page. Web page to gather information you can send to IBM Support




Related tasks
Using asynchronous beans

Reference topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/asyncbns/ref/rasb_troubleshoot.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)