| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ME01: WMQ - Initial Context Factory - Connection drop |
« View previous topic :: View next topic » |
| Author |
Message
|
| Maximus |
 Posted: Fri Jan 29, 2010 10:00 am Post subject: ME01: WMQ - Initial Context Factory - Connection drop |
 |
|
Acolyte
Joined: 14 Jun 2004
Posts: 57
|
Hi Guys,
We are using the following support pack which uses MQ to store JNDI objects:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24004684&loc=en_US&cs=utf-8&lang=en
We are having a disconnect/timeout problem with ME01, that is happening in Java programs and also in IBM WebSphere Explorer in the "JMS Administered Object" view.
I connect to a JNDI, using "IBM WebSphere Explorer --> JMS Administered Object--> Connect" and then don't use it for a certain time, which cause the connection to MQ to drop and then when ever I want to edit an entry, I get the following error:
com.wm.app.b2b.server.jms.JMSSubsystemException: javax.naming.NamingException: Unable to retrieve actual object from queue. The exception was: javax.jms.JMSException: MQJMS2008: failed to open MQ queue SYSTEM.MQCONTEXT.ADMIN.QUEUE [Root exception is javax.jms.JMSException: MQJMS2008: failed to open MQ queue SYSTEM.MQCONTEXT.ADMIN.QUEUE]
Is there a way to configure the SVRCONN used to connect to the JNDI to NOT drop the connection after a certain time?
We have the problem with WMQ 6.x and 7.x.
Best regards. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jan 29, 2010 12:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Yes,
Do not use ME01.
If you're not using the JNDI of an appserver like WAS use the file based JNDI context. You'll be way closer to a real J2EE context than with ME01.
In my opinion ME01 is a shortcut for JNDI often used in demos that would probably gain to be phased out for the file context. It's a bit more work and more static if you want to build a demo, but IMHO it's way worth the extra mile. I don't think it(ME01) should be used in anything but a demo context and is not fit for enterprise level, but then that's just my opinion.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Maximus |
| Posted: Fri Jan 29, 2010 12:32 pm Post subject: |
|
|
Acolyte
Joined: 14 Jun 2004
Posts: 57
|
| fjb_saper wrote: |
Yes,
Do not use ME01.
If you're not using the JNDI of an appserver like WAS use the file based JNDI context. You'll be way closer to a real J2EE context than with ME01.
In my opinion ME01 is a shortcut for JNDI often used in demos that would probably gain to be phased out for the file context. It's a bit more work and more static if you want to build a demo, but IMHO it's way worth the extra mile. I don't think it(ME01) should be used in anything but a demo context and is not fit for enterprise level, but then that's just my opinion.
Have fun |
Thanks for your comment.... you re-assure me, because I am currently converting to FSContext. I think its kind of overkill to use a QMGR to store something like 30 JNDI entries...
My only issue now is to find a "sharedrive" where I can put the ".bindings" file, instead of spreading the file to who ever needs it.
Regards. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
