This week's book giveaway is in the Artificial Intelligence and Machine Learning forum.
We're giving away four copies of Zero to AI - A non-technical, hype-free guide to prospering in the AI era and have Nicolò Valigi and Gianluca Mauro on-line!
See this thread for details.
Win a copy of Zero to AI - A non-technical, hype-free guide to prospering in the AI era this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

enlist failed while accessing MQ

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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


Thanks
 
srinivas muni
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any Help guys ?
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi svm muni,
Did you find a solution to the above? I'm getting a similar problem.


 
srinivas muni
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Robbie Knight
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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:



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
     
    girl power ... turns out to be about a hundred watts. But they seriuosly don't like being connected to the grid. Tiny ad:
    Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    reply
      Bookmark Topic Watch Topic
    • New Topic