| Author |
Message
|
| Ninja_gts |
 Posted: Sat Jan 19, 2019 11:25 am Post subject: IIB 10 Message Broker Getting stucked when mapped to MQ |
 |
|
Newbie
Joined: 14 May 2018
Posts: 7
|
Hi all,
I am having two IIB 10.0.0.13 message broker running on linux server mapped to single WebSphere MQ Queue Manager v9.
When I creates 3rd message broker and map it to existing Queue Manager , newly created broker (i.e 3rd broker) failing to give any response. Any change to it is not getting reflected and neither it allowing to create integration server on the node.
I tried removing queue manager from broker and creating integration server on it . It's getting successfully created.
Please help me to troubleshoot this problem.
Thanks
Ninja |
|
| Back to top |
|
 |
| mpong |
| Posted: Sat Jan 19, 2019 1:56 pm Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
| how did you create the first tow nodes and associate to QM? is there any steps that are followed differently for creating the 3rd node? Did you look at the logs? |
|
| Back to top |
|
|
| Ninja_gts |
| Posted: Sun Jan 20, 2019 2:31 am Post subject: |
|
|
Newbie
Joined: 14 May 2018
Posts: 7
|
Hi mpong,
Below is the command used for creation of broker.
mqsicreatebroker IIBNODE_N3 -b default -q MQLOCAL
Only the difference in the earlier broker is that , broker listener is disabled.
Now i identified that when i enable broker listener , broker stops responding and works fine when broker listener is disabled.
Issue persist when i enables the broker listener and for same i m not getting any error logs.
Thanks
Ninja |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Mon Jan 21, 2019 1:37 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
|
| Back to top |
|
|
| Ninja_gts |
| Posted: Wed Jan 23, 2019 10:38 am Post subject: |
|
|
Newbie
Joined: 14 May 2018
Posts: 7
|
Hi,
I would like to confirm that listener port of all the brokers are different and two of my node is configured on embedded listener ,I tried 3rd broker with node listener so that on same port I can host number of services by creating multiple execution group.
I am having services which consist of only either MQOUTPUT node MQINPUT node or both. Is this nodes have any restrictions on sharing multiple node with same Queue Manager? Link provided for restriction
does not contains any reference related these node but still I m facing the issue.
Same configuration was implemented on another server and it's working fine.
Thanks
Ninja |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 23, 2019 10:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Ninja_gts wrote: |
| I would like to confirm that listener port of all the brokers are different and two of my node is configured on embedded listener ,I tried 3rd broker with node listener so that on same port I can host number of services by creating multiple execution group. |
All the ports you use must be unique; you can't use the same port as any other broker or node listener. That's a TCP/IP restriction not a broker one. If the designated port is already in use, the component will must likely hang as you describe trying to attach to it. After some period it might throw a timeout error but it might not depending on your settings, or throw it after an unfeasibly long time.
| Ninja_gts wrote: |
| I am having services which consist of only either MQOUTPUT node MQINPUT node or both. |
Then why are you associating a queue manager with the broker at all? Why not just have the MQ nodes client onto a queue manager?
| Ninja_gts wrote: |
| Same configuration was implemented on another server and it's working fine. |
The same configuration down to the port numbers being used?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 25, 2019 5:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Using the broker wide listener assumes that there is a qmgr associated with the broker. I.E. each broker has its own queue manager.... So working as designed...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 25, 2019 5:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Using the broker wide listener assumes that there is a qmgr associated with the broker. I.E. each broker has its own queue manager.... So working as designed... |
I'm enlightened by new knowledge. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 25, 2019 5:55 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
That's because the broker wide listener uses WS_XXXINPUT queue under the covers or a queue name something like that. Check it out in the infocenter.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
