| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Java Program cannot post to Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| merlin |
 Posted: Sun Mar 07, 2004 12:45 pm Post subject: Java Program cannot post to Queue |
 |
|
Novice
Joined: 07 Mar 2004
Posts: 19
|
Hi,
hopefully the problem I am experiencing is a familiar one to someone reading this, cos its got me stumped...
We currently have a program working which reads from local queues and writes to remote queues, where there are 2 separate instances of MQ running, one on iSeries, the other on Windows. There is one queue manager on each platform, which are clustered.
The set up works fine and is currently in production.
Now for the problem: we have been having issues with the Windows 2003 server occasionally failing and self-rebooting, and so decided to use a Windows 2000 server which we know to be stable on which to install MQ 5.3 (along with latest fix pack). The new queue manager has been successfully added to the cluster and I can put and get test messages just fine through the MQ Explorer, but when I run the java program and it tries to connect to the Windows MQ server, it fails with:
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2058
I must stress I don't get any problem running the same code on the 2003 server and I don't believe there was any special configuration applied to that box to get the program working.
Looking into this problem, I noticed that my SYSTEM.DEF.SVRCONN is showing inactive in MQ Explorer on the Windows server where the java program doesn't work, though it shows as 'running' on the 2003 server where java works fine.
Any help would be very much appreciated! |
|
| Back to top |
|
 |
| clindsey |
| Posted: Sun Mar 07, 2004 2:51 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
2058 is MQRC_Q_MGR_NAME_ERROR. Compare the name of the queue manager on your Win 2000 machine with the name the program is using when it does the connect. Remember, it is case sensitive. If your queuemanager object has a null queue manager name, then check the queue manager definition and make sure it is the default qmgr.
Charlie |
|
| Back to top |
|
|
| merlin |
| Posted: Mon Mar 08, 2004 9:26 am Post subject: |
|
|
Novice
Joined: 07 Mar 2004
Posts: 19
|
thanks for the reply Charlie,
turns out that this was a 'simple' issue in the Listener under MQ Services window: connection name was the machine's resolvable name, and Services showed it as Running.
However running 'netstat' in a cmd window proved that there was nothing listening on 1414, only when I changed the connection name in the Listener in MQ Services to '127.0.0.1' and reran did it actually start listening on 1414.
I've lost plenty of time on this and am not impressed, specially since MQ was telling me that the listener was running fine. |
|
| 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
|
|
|
|
