enlist failed while accessing MQ

Hi ,
I have an application that will access queue on a regular basis( I am using WAS 6.1 and MQ 7.0)
Actually there are couple of jobs ( job 1 runs for every 10 mins access Q1 and job 2 runs for every 1 min access Q2) that will read the queue.
When job 1 tries to access the Queue, I am getting enlist failed exception. Job 2 is running fine.
Is the issue related to partner log becoming full ? ( in that case job 2 should also get the same exception. But I dont see any )
No issues with the code ( I verified with couple of my frds). I am not sure what is the exact use of partner log for WAS.

Below is the xception

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
	at com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverableUnit(MultiScopeRecoveryLog.java:1265)
	at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit(RecoveryLogImpl.java:168)
	at com.ibm.ws.Transaction.JTA.PartnerLogData.logData(PartnerLogData.java:204)
	at com.ibm.ws.Transaction.JTA.PartnerLogData.logRecoveryEntry(PartnerLogData.java:160)
	at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(RegisteredResources.java:627)
	at com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(TransactionImpl.java:3306)
	at com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet.java:407)
	at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:699)
	at com.ibm.ejs.j2c.ConnectionEventListener.interactionPending(ConnectionEventListener.java:940)
	at com.ibm.ejs.jms.JMSManagedSession.interactionPending(JMSManagedSession.java:1079)
	at com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java:918)
	at com.ibm.ejs.jms.JMSMessageConsumerHandle.enlist(JMSMessageConsumerHandle.java:809)

00000376 XATransaction E   J2CA0030E: Method enlist caught javax.transaction.SystemException
	at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(RegisteredResources.java:638)
	at com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(TransactionImpl.java:3306)
	at com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet.java:407)
	at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:699)
	at com.ibm.ejs.j2c.ConnectionEventListener.interactionPending(ConnectionEventListener.java:940)
	at com.ibm.ejs.jms.JMSManagedSession.interactionPending(JMSManagedSession.java:1079)
	at com.ibm.ejs.jms.JMSManagedSession.enlist(JMSManagedSession.java:918)
	at com.ibm.ejs.jms.JMSMessageConsumerHandle.enlist(JMSMessageConsumerHandle.java:809)
	at com.ibm.ejs.jms.JMSMessageConsumerHandle.receiveNoWait(JMSMessageConsumerHandle.java:614)
.................

Caused by: com.ibm.ws.recoverylog.spi.InternalLogException
	at com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverableUnit(MultiScopeRecoveryLog.java:1265)
	at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit(RecoveryLogImpl.java:168)
	at com.ibm.ws.Transaction.JTA.PartnerLogData.logData(PartnerLogData.java:204)
	at com.ibm.ws.Transaction.JTA.PartnerLogData.logRecoveryEntry(PartnerLogData.java:160)
	at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(RegisteredResources.java:627)
	... 37 more while trying to enlist resources from datasource xxxxx  with the Transaction Manager for the current transaction, and threw a ResourceException.
ConnectionEve A   J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource xxxx  .  The exception which was received is javax.jms.JMSException: Enlist failed
The Connection Manager received a fatal connection error from the Resource Adapter for resource jms/xxxx .  The exception which was received is javax.jms.JMSException: Enlist failed
Error reading message from Queue Q1

Thanks

Any Help guys ?

Hi svm muni,
Did you find a solution to the above? I'm getting a similar problem.

Hi Robbie Knight , Yes I found the Exact problem. It is related to the partners log becoming full.( IBM released a patch to resolve the issue ). What exactly is your issue. May be I can help you

I resolved it already, but thanks...

It wasn't quite the same error you were getting, but the 2 stack traces have the following line in common:

We had migrated from a WAS 7.0.0.19 installation on a Linux box to a AIX (UNIX) machine. When our EJBs attempted to connect to Oracle 10g using the data source setup, we would get a stack trace as follows:

[1/9/12 11:22:03:427 SAST] 00000037 XATransaction E   J2CA0030E: Method enlist caught javax.transaction.SystemException
        at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredResources.java:1089)
        at com.ibm.ws.tx.jta.TransactionImpl.enlistResource(TransactionImpl.java:2168)
        at com.ibm.ws.tx.jta.TranManagerSet.enlist(TranManagerSet.java:526)
        at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:715)
        at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(ConnectionManager.java:2206)
        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.lazyEnlist(WSRdbManagedConnectionImpl.java:2569)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java:714)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java:2745)
        at org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:166)
        ...
        at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
        at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
        at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: com.ibm.ws.recoverylog.spi.InternalLogException
        at com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverableUnit(MultiScopeRecoveryLog.java:1266)
        at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit(RecoveryLogImpl.java:168)
        at com.ibm.tx.jta.PartnerLogData.logData(PartnerLogData.java:220)
        at com.ibm.tx.jta.PartnerLogData.logRecoveryEntry(PartnerLogData.java:168)
        at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredResources.java:1078)
        ... 61 more
while trying to enlist resources from DataSource jdbc/oracleDb with the Transaction Manager for the current transaction, and threw a ResourceException.
00000037 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
        at com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.createRecoverableUnit(MultiScopeRecoveryLog.java:1266)
        at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.createRecoverableUnit(RecoveryLogImpl.java:168)
        at com.ibm.tx.jta.PartnerLogData.logData(PartnerLogData.java:220)
        at com.ibm.tx.jta.PartnerLogData.logRecoveryEntry(PartnerLogData.java:168)
        at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredResources.java:1078)
        at com.ibm.ws.tx.jta.TransactionImpl.enlistResource(TransactionImpl.java:2168)
        at com.ibm.ws.tx.jta.TranManagerSet.enlist(TranManagerSet.java:526)
        at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:715)
        at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(ConnectionManager.java:2206)
        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.lazyEnlist(WSRdbManagedConnectionImpl.java:2569)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java:714)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java:2745)
        at org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:166)
        ...
        at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
        at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
        at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
        at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

It turns out the Oracle driver (we were using ojdbc14.jar i.e. version 1.4 of the jar) wasn't compatible with the AIX/WAS7 installation. Once we upgraded the driver (to version 6 - ojdbc6_g.jar), the problem went away.

More symptoms were:

Doing a 'test' connection from the admin console does not throw an error

If the JDBC provider is set to Non XA, then the problem goes away

I hope this helps someone else