J2CA0030E for JMS resources and WTRN0000E errors lead to java.lang.OutOfMemoryError
 Technote (troubleshooting)
 
Problem(Abstract)
The tranlogs and partnerlogs fill up rapidly for JMS connections. This causes WTRN0000E errors. The tranlog and partnerlog processing can also cause a java.lang.OutOfMemoryError.

The following messages may be logged:
[1/24/05 12:39:16:996 EST] 12bce43 SystemErr R java.lang.OutOfMemoryError

SystemOut.log.WLM_server1
[1/24/05 12:39:07:774 EST] 1558d83 XATransaction E J2CA0030E: Method enlist caught javax.transaction.SystemException
com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet.java:491
com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:61
at java.lang.Thread.run(Thread.java:534)

while trying to enlist resources from datasource
JMS$xaQCF$JMSManagedConnection@33046559 with the Transaction Manager for
the current transaction, and threw a ResourceException.
[1/24/05 12:39:07:786 EST] 1558d83 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource
Adaptor for resource JMS$xaQCF$JMSManagedConnection@33046559. The exception which was received is javax.jms.JMSException: Enlist failed
[1/24/05 12:39:07:792 EST] 1558d83 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource informed/xaQCF. The exception which was received is javax.jms.JMSException: Enlist failed
[1/24/05 12:39:07:868 EST] 1fb49f6 PartnerLogDat E WTRN0000E: An internal error occurred in method logData in class com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.spi.InternalLogException

JMS traces show:
com.ibm.ws.Transaction.JTA.PartnerLogData; the exception stack trace follows: com.ibm.ws.recoverylog.sp.LogFullException at?
 
Cause
Transaction Logs can fill up quickly due to the number of JMS entries created.
 
Resolving the problem
APAR PQ90843 was created to reduce the number of JMS recovery objects that are stored in the transaction logs and is included in WebSphere® 5.1.1.1

A possible work-around is to do the following:
1. Increase the size of the transaction logs.
Add the size to the transaction log path in the configuration of the Application Server (server.xml):
transactionLogDirectory=".../tranlog/server_name/transaction;xM"
- Where, x denotes the size of the transaction logs in MB (default = 1 MB).
- server_name denotes name of server defined in your configuration.
- Note that in a cluster you need to change the server.xml file for all cluster members.
- Note also, transactionLogDirectory entry will be added to the server.xml if you enter a transaction l log directory through the Administrative Console, otherwise the there will be no transactionLogDirectory entry in the server.xml file.
(Servers-> Manage Application Servers-> your_app_server. Config tab)
2. Change the Connection Pool setting for "Aged Timeout" to 0.
Note: The default is 0, but is commonly changed during configuration of an application.
 
 
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: 5.1.0.6
Software edition:
Reference #: 1200384
IBM Group: Software Group
Modified date: May 25, 2005