| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ Port conflict Issue with other Application |
« View previous topic :: View next topic » |
| Author |
Message
|
| skrv |
 Posted: Sun Feb 10, 2013 7:00 am Post subject: |
 |
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
thanks for all your suggestions.
I will be very happy if someone also answer my technical question.
1. Is there any way we can configure MQ to not to use a particuler port?
2. Do i need to change CLUSRCVR channel as well with LOCLADDR parameter to assign a port range? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Feb 10, 2013 7:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| skrv wrote: |
thanks for all your suggestions.
I will be very happy if someone also answer my technical question. |
You have asked a group of folks with years/decades of experience. Yours is not the first instance of port-collisions. As there are 65k ports, we are suggesting that you/your organization join the 20th century at least, and manage the port issue for the entire organization, and not one MQ port at a time.
| skrv wrote: |
| 1. Is there any way we can configure MQ to not to use a particuler port? |
Apparently, no.
| skrv wrote: |
| 2. Do i need to change CLUSRCVR channel as well with LOCLADDR parameter to assign a port range? |
Yes.
As you are most likely aware, the purpose of a CLUSRCVR channel definition is to introduce a queue-manager to the cluster. The CLUSRCVR definition provides the channel definitions to the clustering software at the FR end of the channel, so it can automatically create (or replace) a CLUSSDR channel back to the qmgr that sent the CLUSRCVR definition. The same definition will be shared with PRs as needed.
_________________
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 |
|
|
| mqjeff |
| Posted: Sun Feb 10, 2013 7:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| skrv wrote: |
| 1. Is there any way we can configure MQ to not to use a particuler port? |
Yes. You have been given this method.
| skrv wrote: |
| 2. Do i need to change CLUSRCVR channel as well with LOCLADDR parameter to assign a port range? |
You have been given an answer to this by IBM.
"for some reason", you have decided not to listen to that. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Feb 10, 2013 3:25 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| skrv wrote: |
thanks for all your suggestions.
I will be very happy if someone also answer my technical question.
1. Is there any way we can configure MQ to not to use a particuler port?
2. Do i need to change CLUSRCVR channel as well with LOCLADDR parameter to assign a port range? |
#1 Yes, but not directly. You have to specify a range of ports it can use, presumably excluding the port you can't use, via LOCLADDR. THat range can be thousands of port numbers.
#2. Yes, especially on the CLUSRCVR channels because those channel's definitions are the ones used by the automatic cluster sender channels the majority of the time that your clustered QMs talk to each other. THey recommend also setting it on the CLUSSNDR channels because those channels are used when the QM needs to establish its initial communication with a Full Repository (or after REFRESH CLUSTER with the REPOS YES option), and presumably you don't want to risk that port conflict even those rare times the manual CLUSNDR channel is used.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sun Feb 10, 2013 4:57 pm Post subject: Re: MQ Port conflict Issue with other Application |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
When applications open a TCP port, they can either explicitly specify a port number ("static port"), or have the underlying OS assign a port number ("dynamic or ephemeral port"). Server-side listener ports usually need to be static, while other server-side and client-side ports usually don't. Dynamic port assignment is not entirely random; the underlying OS platform defines the range of port numbers reserved for dynamic use. The range is usually configurable, though the details vary from platform to platform. (IANA suggests reserving ports >49151 for dynamic use, although the OS administrators are free to configure port ranges some other way.)
| skrv wrote: |
| one of the Enterprise application ... is down because their default port 46464 is been used by MQ |
Applications should not request static ports within the platform's dynamic port range. Even if WMQ uses the LOCLADDR channel attribute to manage its own outbound IP/port assignments, that does not stop the OS from dynamically assigning the port to another unrelated process instead ... the Enterprise application would still be down, except now it's because some other application is using its default port, rather than an MQ application. |
|
| 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
|
|
|
|
