| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| IBM MQ integration with Apache ActiveMQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| tczielke |
 Posted: Sun Jun 04, 2017 5:29 am Post subject: |
 |
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
I would also add "buyer beware" on this "feature". The MQ manual seems to clearly state that the CLWLUSEQ of the QMGR only applies to queues that have a CLWLUSEQ attribute. However, it does seem to also work against a QALIAS queue that does not have this attribute. This is probably a "feature" or bug, but IBM would probably also never close the loophole here, too.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
 |
| tczielke |
| Posted: Sun Jun 04, 2017 9:17 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
I have to retract what I have been saying here. 
In my test, the local queue had CLWLUSEQ(QMGR), so when I was toggling the QMGR CWLWUSEQ, the change of behavior I was seeing was based on local queue changing, and not the alias queue! Sorry, about that.
So my testing matches what Peter had posted. So not sure why eniomarques was not able to just set the qlocal definition to have CLWLUSEQ(ANY) and have the desired behavior of messages being distributed across the cluster, even if a qalias was involved.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Jun 04, 2017 3:05 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| tczielke wrote: |
| So not sure why eniomarques was not able to just set the qlocal definition to have CLWLUSEQ(ANY) and have the desired behavior of messages being distributed across the cluster, even if a qalias was involved. |
I suspect he is artificially binding himself to the local instance of the queue either by opening the q unnecessarily for Input, and/or providing the local QM name on the MQOPEN call.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jun 04, 2017 8:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
He'd have to be especially carefull if he is using JMS to define the queue and using a URI. By default if there is no queue manager present in the URI definition of the queue the queue manager will instert itself there...
So the good bet would be to use a cluster alias in the URI. Same thing if the queue is defined in JNDI...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| eniomarques |
| Posted: Mon Jun 05, 2017 6:20 am Post subject: |
|
|
Novice
Joined: 25 May 2015
Posts: 24
Location: Brazil
|
I guess saper is right, the way ActiveMQ is configured should be the problem.
I tried to set the QM attribute, but no luck also. (The queue have the same setup in the other two QMs).
| Code: |
1 : dis qmgr CLWLUSEQ
AMQ8408: Display Queue Manager details.
QMNAME(BAQ01KDG) CLWLUSEQ(ANY)
2 : dis q(SAMEQ)
AMQ8409: Display Queue details.
QUEUE(SAMEQ) TYPE(QALIAS)
ALTDATE(2017-06-05) ALTTIME(10.08.28)
TARGET(SAMEQ.QL) CLUSNL( )
CLUSTER(TESTCLUSTER) CLWLPRTY(0)
CLWLRANK(0) CUSTOM( )
DEFBIND(NOTFIXED) DEFPRTY(0)
DEFPSIST(NO) DEFPRESP(SYNC)
DEFREADA(NO) DESCR( )
GET(ENABLED) PUT(ENABLED)
PROPCTL(COMPAT) SCOPE(QMGR)
TARGTYPE(QUEUE)
3 : dis q(SAMEQ.QL)
AMQ8409: Display Queue details.
QUEUE(SAMEQ.QL) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2017-06-05)
ALTTIME(10.08.34) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLCHNAME( )
CLWLPRTY(0) CLWLRANK(0)
CLWLUSEQ(ANY) CRDATE(2017-06-05)
CRTIME(10.08.34) CURDEPTH(4)
CUSTOM( ) DEFBIND(NOTFIXED)
DEFPRTY(0) DEFPSIST(NO)
DEFPRESP(SYNC) DEFREADA(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ( ) IPPROCS(0)
MAXDEPTH(5000) MAXMSGL(4194304)
MONQ(LOW) MSGDLVSQ(PRIORITY)
NOTRIGGER NPMCLASS(NORMAL)
OPPROCS(0) PROCESS( )
PUT(ENABLED) PROPCTL(COMPAT)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(FIRST) USAGE(NORMAL)
4 : dis qs(SAMEQ.QL)
AMQ8450: Display queue status details.
QUEUE(SAMEQ.QL) TYPE(QUEUE)
CURDEPTH(4) IPPROCS(0)
LGETDATE( ) LGETTIME( )
LPUTDATE(2017-06-05) LPUTTIME(10.11.50)
MEDIALOG( ) MONQ(LOW)
MSGAGE(105) OPPROCS(0)
QTIME( , ) UNCOM(NO) |
All of the 4 sent messages were sent to the 1st QM only. I tried to restart AMQ, but no luck also. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
