| Author |
Message
|
| ranjan1247 |
 Posted: Thu Dec 25, 2014 8:30 pm Post subject: Can we start two listener with same port number? |
 |
|
Novice
Joined: 17 Feb 2014
Posts: 20
|
Can we start two listener with same port number in different qmgr but the qmgrs belong to same server?
Ok let me expalain
I have a server :XYZ
XYZ server has 2 qmgrs:QM1, QM2
both qmgrs has default listener.I want to start both the listener.
Is it possible to start both the listener? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Dec 25, 2014 9:19 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
Have you tried it? What were 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 |
|
|
| ranjan1247 |
| Posted: Thu Dec 25, 2014 10:31 pm Post subject: |
|
|
Novice
Joined: 17 Feb 2014
Posts: 20
|
yes i tried.
i could not do it.showing errors as
An attempt to bind the TCP/IP socket to the listener port was unsuccessful. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Dec 25, 2014 11:31 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As you have found, you can only have one thing listening on a PORT. This is not an MQ issue but a restriction of the TCP/IP network stack.
Care to explain why you need to have both QMGRS listening on the same port?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ranjan1247 |
| Posted: Fri Dec 26, 2014 12:06 am Post subject: |
|
|
Novice
Joined: 17 Feb 2014
Posts: 20
|
Thank you replying....
Actually QM2 was deactivated but the now they want both the qmgr up .
We need to change the port and reconfigure it |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri Dec 26, 2014 7:28 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
|
| smdavies99 wrote: |
As you have found, you can only have one thing listening on a PORT. This is not an MQ issue but a restriction of the TCP/IP network stack.
Care to explain why you need to have both QMGRS listening on the same port? |
I agree that the configuration to recommend here is having the two queue managers listen on different ports. But just a note that TCP does allow for a listening or passive socket to allow multiple listeners to be able to listen on the same port/socket, based on the SO_REUSEADDR setting (based on my understanding  ). For the MQ distributed listener, I believe allowing only one instance of the listener to listen on a port is done by setting an environment variable like "export AMQ_NO_SO_REUSE=YES". Please note I am NOT recommending that setting here . |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 26, 2014 8:05 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Also note that should you manage to have 2 qmgrs listening on the same port, your second qmgr better be an exact clone of the first one, or you will run into a number of problems too ugly to contemplate. Even though you will run into channel number sequence problems etc...
Should it be possible to have 2 qmgrs listening on the same interface and port , I recommend against it. There is no problem having 2 qmgrs listen on the same port but on a different IP (interface). Just make sure the correct ipaddr information is added to the listener definition. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri Dec 26, 2014 8:17 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
|
| Yes, and just to clarify, I am not recommending that configuration (two queue managers listening on the same port). However, we have run into issues where the MQ listener is listening on a port and another listener (i.e. WAS/JBoss JVM) mistakenly comes along and starts a listener on the same port, which causes channel connectivity problems for our queue manager. One recommendation we got from the MQ support team is that environment variable I mentioned (AMQ_NO_SO_REUSE=YES), which will prevent that from happening. But I also believe running your listener with that setting can also prevent the listener from being able to restart if you have some "lingering" connections against that port, so we do not use that setting for our listener. We just find the WAS/JBoss JVM that is incorrectly configured and get the administrator/app team to correct it . |
|
| Back to top |
|
|
|
|
