| Author |
Message
|
| varunraot |
 Posted: Wed Oct 28, 2015 7:54 am Post subject: |
 |
|
Acolyte
Joined: 01 Jun 2011
Posts: 63
|
Yes. I have deployed on B and not on A. I have tested the flow on B to execute when the message was sent from the port 1431
This is in response to the below question.
What have you done to prove this? Did you deploy a flow to B that you did not deploy to A?
Did you get a test flow on B to execute when you sent a message to port 1431? |
|
| Back to top |
|
 |
| varunraot |
| Posted: Wed Oct 28, 2015 8:15 am Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 63
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 28, 2015 8:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is the queue shared in the cluster...
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| varunraot |
| Posted: Thu Oct 29, 2015 6:59 am Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 63
|
| Yes. Its shared in the cluster. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 7:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| varunraot wrote: |
| Yes. Its shared in the cluster. |
So you put the message on queue manager A. It ended up on the TEST.IN queue on queue manager B, where the flow executed it.
That's how clusters work.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| varunraot |
| Posted: Thu Oct 29, 2015 7:15 am Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 63
|
Ok.
If you refer my screenshot http://screencast.com/t/WYyjo0WDRGeC
we can see ports 1431 and 1432 shared with same queue manager ( say B)
Is it because some other local queue manager ( say A) is having 1432 as port and both local queue manager A & B are sharing the same cluster? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 29, 2015 7:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Ports are not shared between qmgrs.
Ports are not shared in the o/s image.
Use Windoze Process Explorer (or whatever tool you choose) for instances of [url]runmqlsr[/url] in the o/s instance. Do a netstat in the o/s instance. Compare the results.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 29, 2015 7:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I can't see that. My site's network security features have a defensive attitude to websites they don't know or trust.
| varunraot wrote: |
| we can see ports 1431 and 1432 shared with same queue manager ( say B) |
If one queue manager has 2 listeners, one using 1431 and one using 1432 and another queue manager has a single listener using 1431 then the queue manager using 1431 is the first one to open the port rather than a particular queue manager. I commented earlier about your odd cluster configuration and it sounds like your queue manager configuration is as odd.
Especially as at the start of this post you didn't even know there was a second queue manager.
| varunraot wrote: |
| Is it because some other local queue manager ( say A) is having 1432 as port and both local queue manager A & B are sharing the same cluster? |
No. Listeners are not shared in a cluster and are specific to a queue manger. It just sounds like you have badly configured queue managers.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
