This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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.
Hi svm muni,
Did you find a solution to the above? I'm getting a similar problem.
Joined: Oct 04, 2010
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
Joined: Sep 18, 2006
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 126.96.36.199 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:
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