| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBIMB connects to MQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| billzhang1123 |
 Posted: Mon Jul 20, 2009 3:14 pm Post subject: WBIMB connects to MQ |
 |
|
Newbie
Joined: 20 Jul 2009
Posts: 1
|
I have WBIMB V5 CSD 10 and MQ 5.3 fix pack 4 installed on my local machine. The problem I have right now is that WBIMB initial setup wizard doesn't work properly. It's supposed to have configuration created and let WBIMB talk to MQ's queue manager. But it's giving error saying 'configuration manager can't be reached... error code 2195'.
User should have the right security, MQ is up and running. Configuration manager and brokers are up and running.
Can someone give me a clue please? Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jul 20, 2009 3:31 pm Post subject: Re: WBIMB connects to MQ |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| billzhang1123 wrote: |
| Can someone give me a clue please? Thanks. |
If you must use the out of support v5.3 version, at least use something better than fix pack 4; i.e. anything!
There's also no good reason to still be using v5.3.
The 2195 will be accompanied by an FDC file. Investigating that will at least tell you which v5.3 fix pack resolves your problem.
Though your basic problem remains you're using v5.3
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vol |
| Posted: Tue Jul 21, 2009 1:55 am Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009
Posts: 69
|
It is unlikely that 2195 (unexpected error) will be accompanied by an FDC.
The most likely cause is a network or channel failure of some kind, particularly as the error is 'cannot be reached'. Java apps return 2195 after a comms failure. Check the WMQ qmgr error logs for channel comms errors, AMQ9*. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 21, 2009 2:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vol wrote: |
| It is unlikely that 2195 (unexpected error) will be accompanied by an FDC. |
Really? All unexpected errors, by their definition, should throw an FDC so that IBM Support can diagnose them when you raise the PMR.
| vol wrote: |
| The most likely cause is a network or channel failure of some kind, particularly as the error is 'cannot be reached'. Java apps return 2195 after a comms failure. Check the WMQ qmgr error logs for channel comms errors, AMQ9*. |
Not in my experience, and I'd welcome comments from more experienced Java people! Channel failures normally yield a 2009 or 2019, queue manager being initially unreachable give a 2059.
Mind you, v5.3.4 could do anything.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
