| Author |
Message
|
| mickey1691 |
 Posted: Tue Jun 04, 2013 8:02 am Post subject: Broker Listening to Port 80 in Linux |
 |
|
Novice
Joined: 04 Jun 2013
Posts: 19
|
Hi. We're trying to create a broker in Linux that listens in on port 80. So far, we have created the broker, set the port using mqsichangeproperties, and tried to restart the broker.
However, when we try to netstat all the ports being listened to, port 80 is not listed. We also tried posting a request in an HTTPInput URL in a message flow in the broker, but the browser says that "Localhost was rejected."
Any suggestions to this?
Thanks... |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jun 04, 2013 8:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
exactly what mqsichangeproperties command did you specify?
exactly what have you deployed to the broker? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 04, 2013 9:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Remember that any port below 1024 requires priviledged setup! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mickey1691 |
| Posted: Tue Jun 04, 2013 2:40 pm Post subject: |
|
|
Novice
Joined: 04 Jun 2013
Posts: 19
|
mqsichangeproperties <BROKER_NAME> -b httplistener -o HTTPCONNECTOR -n port -v 80
Tried starting the broker using root, but it can't connect to the queue manager. We also tried stopping the queue manager and starting it using root, but root doesn't have enough privileges to start the queue manager. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Jun 04, 2013 11:40 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mickey1691 wrote: |
| ...We also tried stopping the queue manager and starting it using root, but root doesn't have enough privileges to start the queue manager... |
Nor should it, ever!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 05, 2013 4:31 am Post subject: Re: Broker Listening to Port 80 in Linux |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mickey1691 wrote: |
| Any suggestions to this? |
Why not start the broker listener on a port higher than 1024 (7800 for instance) and use a proxy / Apache / network appliance to redirect the port 80 traffic?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jun 05, 2013 2:46 pm Post subject: Re: Broker Listening to Port 80 in Linux |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| No ideas from me, but just wanted to say, this isn't really "WebSphere MQ Installation/Configuration Support" |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jun 05, 2013 6:47 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| fjb_saper wrote: |
| Remember that any port below 1024 requires priviledged setup! |
I'm not sure what you mean by privileged ...
There is really nothing magic about port 80, or other port numbers - other than some are categorized as well-known ports, some are registered ports, and some are dynamic or private ports.
For example, you can use port 80 with WMQ channels if you want. Of course, this might conflict with other applications running in the same o/s instance that may want to use port 80 for other purposes.
_________________
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 |
|
|
| exerk |
| Posted: Wed Jun 05, 2013 11:33 pm Post subject: Re: Broker Listening to Port 80 in Linux |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mvic wrote: |
| No ideas from me, but just wanted to say, this isn't really "WebSphere MQ Installation/Configuration Support" |
Good point so moving this to the Broker forum...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Jun 06, 2013 12:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| bruce2359 wrote: |
| I'm not sure what you mean by privileged ... |
At least for Unix-like platforms, binding to well-known ports (in the range from 0 to 1023) requires superuser privileges. The userids for qmgr and broker processes typically don't have superuser privileges, which makes it more difficult for those processes to bind directly to well-known ports. |
|
| Back to top |
|
|
| mickey1691 |
| Posted: Thu Jun 06, 2013 7:33 pm Post subject: Re: Broker Listening to Port 80 in Linux |
|
|
Novice
Joined: 04 Jun 2013
Posts: 19
|
| Vitor wrote: |
| mickey1691 wrote: |
| Any suggestions to this? |
Why not start the broker listener on a port higher than 1024 (7800 for instance) and use a proxy / Apache / network appliance to redirect the port 80 traffic? |
I found you can use authbind that allows programs to bind to the port, but I'm not sure if it can be used on mqsi commands. Anybody else with experience from using authbind with message broker? |
|
| Back to top |
|
|
|
|
