Error Cc=2 Rc=2189 Cannot Open
Contents |
RSS Feed - WebSphere MQ mq error code 2033 Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » Clustering » WebSphere Application Server and MQMq Error Code 2085
Clusters WebSphere Application Server and MQ Clusters « View previous topic :: View next topic » Author Message flwilliams87 Posted: Wed Dec 19,
Mq Error Codes
2007 7:50 am Post subject: WebSphere Application Server and MQ Clusters AcolyteJoined: 04 Feb 2003Posts: 66Location: Chicago, IL Does any version of WAS (WebSphere Application Server), allow it's Queue Manager to be part of an MQ
Mq Completion Code 2 Reason 2033
Cluster?_________________IBM Certified WebSphere MQ Administrator Back to top jefflowrey Posted: Wed Dec 19, 2007 7:55 am Post subject: Grand PoobahJoined: 16 Oct 2002Posts: 19981 Every version does._________________I am *not* the model of the modern major general. Back to top flwilliams87 Posted: Wed Dec 19, 2007 8:25 am Post subject: Using the JMS Engine? AcolyteJoined: 04 Feb 2003Posts: 66Location: Chicago, IL Using the JMS Engine?_________________IBM Certified WebSphere MQ Administrator Back to top jefflowrey Posted: Wed mq error codes pdf Dec 19, 2007 8:49 am Post subject: Grand PoobahJoined: 16 Oct 2002Posts: 19981 I really don't know what you mean. MQ is a JMS engine._________________I am *not* the model of the modern major general. Back to top jefflowrey Posted: Wed Dec 19, 2007 8:51 am Post subject: Grand PoobahJoined: 16 Oct 2002Posts: 19981 Also, WAS instances don't have "their own" Queue Managers in the same way that Broker does._________________I am *not* the model of the modern major general. Back to top flwilliams87 Posted: Wed Dec 19, 2007 9:18 am Post subject: Bad Question... AcolyteJoined: 04 Feb 2003Posts: 66Location: Chicago, IL Forget the second question it was a typo but I have everything I need so thanks._________________IBM Certified WebSphere MQ Administrator Back to top fjb_saper Posted: Wed Dec 19, 2007 2:47 pm Post subject: Re: Using the JMS Engine? Grand PoobahJoined: 18 Nov 2003Posts: 18620Location: LI,NY flwilliams87 wrote: Using the JMS Engine? If you are talking about WAS 6 with the JMS Engine you will need multiple instances of the JMS Engine on the SIBUS to achieve redundancy, failover and load balancing.... Have fun _________________MQ & Broker admin Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First Page 1 of 1 MQSeries.net Forum Index » Clustering » WebSphere Application Server and MQ Clusters
had put together for the developers. But it never occurred to me that they might be using qmgr name in the Open in this particular case. Yes, the https://www.mail-archive.com/mqseries@akh-wien.ac.at/msg14002.html application is probably using it, I was told. I cannot look at their code. I have been told that Smalltalk binding involves getting a Queue Manager connection, and passing that connection to the Open operation. Therefore QMAlias would not work (as they would have to connect to this QMAlias first, as part of their start-up proc in their ini file ). This will take them some time to investigate as the developer mq error of the app is gone. I will post my findings/resolution. Thanks again, Ruzi --- Neil Casey <[EMAIL PROTECTED]> wrote: > Hi Ruzi, > > check to see that the application MQOD which is > opened for output does not > contain a queue manager name. > > If the application puts the local queue manager name > (QM1 in your case) > into this field, it stops cluster name resolution > from mq error code working properly. Of > course the 'q' program and amqsputc don't do this, > so they will work. > > If your application forces a non-blank queue manager > name (at my site we > use Roma which enforces a non-blank QM name in MQOD > on MQOPEN), then you > can get around this by creating a dummy queue > manager alias. > > That is, you: > DEFINE QR(CLUSTER.QM) DESCR('Cluster QM Alias to map > to blank QM name') > (There are no other parameters required) > > on QM1. Your client app which specifies CLUSTER.QM > as the QM name on the Q > open will now resolve to a cluster queue as the QM > name is mapped by the > QMAlias to spaces. > > As an alternative to this, you can create the QR > (CLUSTER.QM) as a cluster > visible q on the QM(s) with the target queue. The > resolution will then go > via the alias, instead of resolving the queue name. > > Regards, > > Neil Casey. > > > |---------+----------------------------> > | | Ruzi R | > | | <[EMAIL PROTECTED]| > | | M> | > | | Sent by: MQSeries| > | | List | > | | <[EMAIL PROTECTED]|
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 17:52:33 GMT by s_ac15 (squid/3.5.20)