| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Connecting Problems with WAS 5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| szoerner |
 Posted: Wed Dec 11, 2002 12:34 am Post subject: Connecting Problems with WAS 5 |
 |
|
Newbie
Joined: 11 Dec 2002
Posts: 1
|
Hello!
Our application runs on WebSphere AppServer 4.0.3 (W2k) and connects to a MQSeries 5.2 queue manager on OS/390 via JMS.
We tried to migrate to WAS 5 and have problems with establishing a connection to MQ. The same WebApp works fine with WAS 4.03 or the WSAD 4 Test Environment, but fails to connect when running in WSAD 5 Test Environment or a WAS 5. We do not use the embedded MQ-Server in WAS 5.
We isolated the Problem to ten lines of code (no JNDI, no JMS). It does not matter whether we use JMS or base classes, or whether the MQ is running on OS/390 or another Win2k machine. The code runs fine in an main-class in WSAD 5. In WAS 5 we get the following errors:
On the MQ client (the WAS 5 on Win2k):
MQException
MQJE025: Channel closed after two initial changes. Closure reason {0}
MQJE001: Completion Code 2, Reason 2009
On the MQ Server (running on Win2k, Win2k Event log):
"AMQ9503 Channel negotiation failed"
It seems like the connection is established, but due to any problem it is closed bei the Queue Manager immediatly (?).
Any help or idea is welcome !!!
Greetings, Stefan
--8<-----
Stefan Zoerner
Sun Certified Web Component Developer for J2EE |
|
| Back to top |
|
 |
| kingdon |
| Posted: Wed Dec 11, 2002 4:22 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
Hi Stefan,
I can only give you the same answer as on the ibm.software newsgroup - please raise a problem against MQ through your service contract.
Were you hoping for something different?
Regards,
James. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Jan 07, 2003 12:57 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Since this may come up again....I just encountered this problem, and actually ended up with a solution. My problem was the fact that I didn't have at least CSD4 on the 5.2 Qmgr. Once I moved to CSD4, things started working. |
|
| 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
|
|
|
|
