| Author |
Message
|
| mq_user |
 Posted: Fri Jul 14, 2006 7:25 am Post subject: WAS-MQ |
 |
|
Newbie
Joined: 10 Jul 2006
Posts: 9
|
Hi All,
I am running two instances of the same application on a websphere application server. Each instance has to connect to each queue manager on the a different mq server. The MQ server has 2 queue managers, with different names aand same set of queues, listening on different listener ports and channels.I set the host name and the queue manager name in a properties file which will be loaded during the application startup. But this connection is failing for one instance....it works for the other instance.
Any ideas on why this should happen...and how should I go about fixing this???
Any help on this one is greatly appreciated.
Thanks. |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Fri Jul 14, 2006 9:11 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
What is the MQ reason code? Secondly, how do you know the second application is correctly setting the MQ info? What does your application log show about the information being used? (i.e. no assumption)
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| mq_user |
| Posted: Fri Jul 14, 2006 3:55 pm Post subject: |
|
|
Newbie
Joined: 10 Jul 2006
Posts: 9
|
| The error is failed to connect to queue manager QMANAGER NAME. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Fri Jul 14, 2006 7:12 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| mq_user wrote: |
| The error is failed to connect to queue manager QMANAGER NAME. |
That's not the MQ Reason Code. It is almost impossible to help you unless we know the MQ Reason Code AND what parameters are used for your MQ information.
Set your application in a verbose logging mode and dump out what your application is using for:
- Queue Manager Name
- Channel Name
- hostname
- Port number
Please take the time to gather the appropriate information otherwise we cannot help you.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Jul 17, 2006 11:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I'd also be curious to know if it always failing to the same qmgr. Or, does it always fail on the connect to the first or second one regardless of which qmgr it is? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 17, 2006 2:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you per chance trying to connect to 2 different qmgrs in the same thread at the same time?
i.e. connecting to the 2nd one while the connection to the first one has not been closed ? And both in "bindings" mode??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mq_user |
| Posted: Thu Jul 20, 2006 6:57 am Post subject: |
|
|
Newbie
Joined: 10 Jul 2006
Posts: 9
|
| I think the name of the queue manager is hard coded in the application code.....but the development team thinks otherwise...It fails to connect if I use any other name other than the one that always connects .........Any Ideas?..... |
|
| Back to top |
|
|
|
|
