| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Linux and HTTPListener not listening |
« View previous topic :: View next topic » |
| Author |
Message
|
| fazz |
 Posted: Wed Sep 27, 2006 1:24 am Post subject: Linux and HTTPListener not listening |
 |
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Hello all,
I'm having a problem with the HTTPListener process on Linux, it does not seem to be listening on the specified port (7081).
I have deployed a working flow (tested on a Windows machine) that contains an HTTP Input and HTTP Reply node to a Linux broker.
I stopped the Broker and changed the port from the default (7080) to 7081 because it was in use by another process.
I then started the broker, but I cannot hit the service using NetTool, and if I run 'netstat -a|grep LISTEN', I cannot see anything using 7081.
I have checked the HttpListenerPort file located under /var/mqsi/registry/broker_name and it specifies 7081, I have also turned on tracing for the listener and it seems to be reporting no problems.
I have checked the messages log file, and no errors are reported there.
I have also tried using 7080 and stopping the other process that was using it to no avail.
Does anyone have any ideas?
Thanks |
|
| Back to top |
|
 |
| jbanoop |
| Posted: Wed Sep 27, 2006 3:51 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Did you try deplying a flow that actually has to use the http listener. I am not quite sure but i think it would be started (if not started already) when you deploy a flow which uses webservices.
It is worth a try.
Regards,
Anoop |
|
| Back to top |
|
|
| fazz |
| Posted: Wed Sep 27, 2006 4:17 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Yes I have deployed a flow with an HTTP Input and HTTP Reply node.
I think you are right, it only starts up if needed. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 27, 2006 4:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In version 5, the biphttplistener process doesn't start until you deploy a flow that uses an HTTPInput node.
In version 6, the biphttplistener process starts and stops when the broker does. It does not open the port for LISTENing until you deploy a flow that uses an HTTPInput node.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fazz |
| Posted: Wed Sep 27, 2006 5:10 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
| Yes, and thats the problem, I have deployed a flow, I can see the biphttplistner process, but there is nothing listening on the specified port. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
