Author |
Message
|
angka |
Posted: Wed Mar 26, 2008 12:01 am Post subject: 2 Sender to 1 Receiver |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi,
QM1 and QM2 connect to QM3 via the same receiver channel 'QM3channel' so there were be 2 saved status on QM3 receiver. So when either QM1 or QM2 try to establish a connection with QM3 via 'QM3channel', how does MQ choose which saved status to choose? Which attributes in the saved status are compared?
Thank you. |
|
Back to top |
|
 |
AkankshA |
Posted: Wed Mar 26, 2008 12:20 am Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
fundu question.....
could not resist myself trying it
I guess it creates instances of multiple channels itself
abc is the receiver channel common for 2 sender channels
display chstatus('abc')
AMQ8417: Display Channel Status details.
CHANNEL(abc) CHLTYPE(RCVR)
CONNAME(127.0.0.1) CURRENT
RQMNAME(aa) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( )
AMQ8417: Display Channel Status details.
CHANNEL(abc) CHLTYPE(RCVR)
CONNAME(127.0.0.1) CURRENT
RQMNAME(bb) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( ) _________________ Cheers |
|
Back to top |
|
 |
angka |
Posted: Wed Mar 26, 2008 1:01 am Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi,
So you mean the attributes compared is RQMName only?? so if my QM1 and QM2 is the same name, when either of them try to establish connection with QM3, the receiver channel will confuse? and the sequence number may be off?
Thank you. |
|
Back to top |
|
 |
AkankshA |
Posted: Wed Mar 26, 2008 1:08 am Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
well isn't that maintained by sender channel
i just did runmqsc on sender qm..
display chstatus('abc') CURSEQNO
11 : display chstatus('abc') CURSEQNO
AMQ8417: Display Channel Status details.
CHANNEL(abc) CHLTYPE(SDR)
CONNAME(localhost(1416)) CURRENT
CURSEQNO(1) RQMNAME(cc)
STATUS(RUNNING) SUBSTATE(MQGET)
XMITQ(cc) _________________ Cheers |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 26, 2008 1:42 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
angka wrote: |
so if my QM1 and QM2 is the same name |
You should not have 2 queue managers with the same name in your estate
angka wrote: |
when either of them try to establish connection with QM3, the receiver channel will confuse? |
IIRC the receiver MCA uses the UUID of the sender. But I wouldn't like to bet my production system on it.
If you have QM1 and QM2 (called that) both using "QM3Channel" to talk to QM3 it works a treat. If you have 2 queue managers called QM1 doing that I'm not sure what would happen, apart from your request/reply model being up the creek & you can never use clustering.
Is this 2-queue-managers-with-the-same-name intended as some kind of poor man's failover? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
angka |
Posted: Wed Mar 26, 2008 7:29 pm Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi,
The QM is of different name. I raised this question because the connection always has Sequence number out issue. Since it is comparing the UUID i believe that it maybe cos by other problem
Thank you. |
|
Back to top |
|
 |
AkankshA |
Posted: Wed Mar 26, 2008 8:03 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
angka wrote: |
Hi,
The QM is of different name. I raised this question because the connection always has Sequence number out issue. Since it is comparing the UUID i believe that it maybe cos by other problem
Thank you. |
You mean you have such a design existing in your environment....
i better stop cribbing about mine then.... _________________ Cheers |
|
Back to top |
|
 |
Vitor |
Posted: Thu Mar 27, 2008 1:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
angka wrote: |
The QM is of different name. I raised this question because the connection always has Sequence number out issue. Since it is comparing the UUID i believe that it maybe cos by other problem
|
There's no reason why you can't do point to point with 2 senders running into a single receiver. I've been on a site where it was used exclusively and there was never a sequence problem that wasn't attributable to other causes.
Before anyone says anything I know it can cause problems doing that but there was a conscious decision to do it that way and take any problems on the chin by site management. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
angka |
Posted: Tue Oct 28, 2008 12:23 am Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi,
How to view the UUID?? If the Sender is using MQ V5.1 and Receiver is using MQ V6.0.2.1, will there be any problem having 2 Sender to one receiver??
Thanks |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 28, 2008 2:02 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
angka wrote: |
How to view the UUID?? |
It's a queue manager attribute.
angka wrote: |
If the Sender is using MQ V5.1 and Receiver is using MQ V6.0.2.1, will there be any problem having 2 Sender to one receiver??
|
Nothing compared to the problem of using v5.1 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 28, 2008 3:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Oh my. Welcome back, Vitor! |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 28, 2008 4:26 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Oh my. Welcome back, Vitor! |
It's good to be back, even if I'm only partially back. The call of a thread update was too strong to resist.... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
HubertKleinmanns |
Posted: Tue Oct 28, 2008 4:31 am Post subject: |
|
|
 Shaman
Joined: 24 Feb 2004 Posts: 732 Location: Germany
|
maybe angka uses MQSeries for Compaq Tru64 Unix - this is the only platform, where MQv5.1 is still supported . _________________ Regards
Hubert |
|
Back to top |
|
 |
|