After installing a fix pack or cumulative fix, WTRN0040W warnings may be logged in the SystemOut.log when starting
 Technote (troubleshooting)
 
Problem(Abstract)
After installing an IBM® WebSphere® Application Server Fix Pack or Cumulative Fix for V5.0, V5.1, or V6.0, a WTRN0040W warning may occur when starting an application server during transaction recovery. Transaction recovery occurs when an application server is started. The transactions to be recovered are in-doubt transactions (xa transactions that were not completed before the application server stopped); the information used to recover these is stored in log files in the tranlog and partnerlog folders.
 
Symptom
If a Fix Pack or Cumulative Fix is installed when there are entries in the tranlog and partnerlog files for an application server, then it is possible that when starting the Application Server, the following error may occur:

WTRN0040W: Object cannot be deserialized. The exception stack trace follows:
java.io.InvalidClassException: com.ibm.ejs.j2c.J2CXAResourceInfo; local class incompatible: stream classdesc serialVersionUID =
6152683146532742988, local class serialVersionUID = -8127210893358178789
 
Cause
The cause of the error is two-fold; there are incomplete transactions in the tranlog and partnerlog files prior to the upgrade and there were changes in the transaction recovery classes in the Fix Pack or Cumulative Fix, specifically in the J2CXAResourceInfo class, that make it impossible for the application server to recreate the stored J2CXAResourceInfo in the tranlog file. Transactions are kept in the tranlog and partnerlog files when xa transactions (two-phase commit (2PC) transactions) until the transaction is either committed or rolled back, which completes the transaction.

Note: one action that can cause transactions to be in an in-doubt state is to terminate the Application Server process using an operating system action, such as terminating the Windows® process or killing the UNIX® OS process.
 
Resolving the problem
There are two possible solutions to the problem.

1. Delete all files in the tranlog and partnerlog directories and restart the Application Server.


For Application Server V6.0, those folders are in the

<install_root>/profiles/ProfileName/cellName/nodeName/serverName/tranlog/<server name> directory.

For Application Server V5.0 and V5.1, those folders are in the

<install_root>/tranlog/<server name> directory.

Note, it is possible simply to delete the tranlog and partnerlog directories.

2. Uninstall the Fix Pack or Cumulative Fix and allow the Application Server transaction manager to complete all of the transactions so that there are none left in the log files in the tranlog and partnerlog directories. Then reinstall the Fix Pack or Cumulative Fix.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Transaction Service (JTS)
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1215914
IBM Group: Software Group
Modified date: Sep 1, 2005