Search...
FAQs Subscribe
Pie
FAQs
Recent topics Flagged topics Hot topics Best topics
Search...
Search within WebSphere Search Coderanch
Advance search Google search
Register / Login
granny thread boost polymorphism book review grid advertise on coderanch
  • 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 Pie Elite all forums
meaningless drivel thread boost building better world book advertise on coderanch book review grid
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

failed to open MQ queue

 
Janhavi Namshikar
Ranch Hand
Posts: 85
I like...
Eclipse IDE Spring Java
posted 19 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hi,
I am getting the following error when I start the server. This is the stack trace :




Can any1 pls help me with this.. I am new to the WebSphere world and I think maybe I have done some setting wrong.

Thanks,
Janhavi.

"Weekends don't count unless you spend them doing something completely pointless."

 
Brian Hennessy
Ranch Hand
Posts: 57
posted 19 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hi
I have seen this recently. I think it may have to do with the set up of the queues from the MQ side rather than the jndi set up of the queues on Websphere. In my case our infrastructure people didn't set my MDB's reply queue as a remote queue. So the home/remote queues were deleted and redefined. However I'm not familar with the MQ commands to give you them but I'm sure they can be found on the web.
 
david lightman
Ranch Hand
Posts: 82
posted 19 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
the 2085 return code means unknown object. In order to 'create a queue', you need to have already defined the queue to your queue manager.
 
Janhavi Namshikar
Ranch Hand
Posts: 85
I like...
Eclipse IDE Spring Java
posted 19 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
The Queues are defined in the queue manager, and from the Administrative console I am doing the following :

Click on
Servers > Application Servers > servername > Server Components > JMS Server.
Then inside the Queue Names text area I enter the names of the queue that are defined in the Queue manager.
All the Q names are entered in different lines, no comma or semicolon is used as seperator. Am I doing something wrong here? or am I suppose to do some other settings for the Q?
I am using WSAD 5.1.0 and WebSphere MQ 6.0


Thanks,
Janhavi

"Weekends don't count unless you spend them doing something completely pointless."

 
david lightman
Ranch Hand
Posts: 82
posted 19 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Yes, there is alot.
That is not where you want to be at all. Instead, go to resources, Websphere MQ JMS providers and add your QueueConnectionFactory and your QueueDestination (which is a pointer to the actual WMQ queue) then add a MessageListenerPort and attach the QCF and Qdest. Yuo should be set afterwards.
 
Web Programmer
Greenhorn
Posts: 2
posted 19 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Janhavi,
It is also important to make sure that when ever you get JMS Exceptions, you obtain the linked Exception as well like
exception.getLinkedException()
This will give the specific error code, with which you will come to know the exact mq exception cause by looking up the mqrc details.

Thanks.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
reply
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!
Similar Threads
More...