Posted: Fri Sep 22, 2006 8:11 am Post subject: WebSphere JMS MDB can't open cluster QALIAS MQRC 2082
Newbie
Joined: 14 Sep 2006 Posts: 5
WebSphere Application Server V.6 on Linux
WebSphere MQ Client V.6.0.1.1 on Linux
Application MQPut->[QM2->QM1]->WAS JMS
QM1 and QM2 are qmgrs in the same Cluster CL1
Clustered QALIAS QA1 is defined on QM1 with targetQ QL1 which is defined as a clustered QLOCAL on QM2.
All Qs and Aliases have DEFBIND(NOTFIXED) because of current problem with DEFBIND(OPEN) (http://www.mqseries.net/phpBB2/viewtopic.php?t=32031)
Appl connects to QM2 and Puts msgs on QL1
Connected to QM1 amqsgetc QA1 happily retrieves these messages.
When we try to get our WAS Message Driven Bean to do the same i.e. get msgs from QA1 on QM1 we get MQRC 2082 UNKNOWN_ALIAS_BASE_Q.
The MDB is in a built-in WAS Container so we don't have much control over the code that is doing the MQ requests.
JMS definition is:
Provider=WebSphere MQ
QCF qmgr="" host="ourhost" port="1414" Transport Type=Client Channel=SYSTEM.DEF.SVRCONN
Queue Desination Base Queue Name="QA1" Base Qmgr="" Target Client="MQ"
I've seen posts talking about using QR to define a cluster alias that can be used in the JMS qmgr field but I can't figure out if that applies in our case or if it is only to allow another qmgr to "see into" the existing cluster.
You can't get from a queue that is not a QLOCAL on the queue manager you are connected to.
That means that if you open a QALIAS for Input, then the QALIAS must resolve to a QLOCAL on the same qmgr.
So if you need to run an MDB against a Queue that is a qlocal on QM2, then the QCF used by the Listener Port for the MDB must point to QM2. _________________ I am *not* the model of the modern major general.
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