| Author |
Message
|
| wraymore |
 Posted: Tue Aug 16, 2005 5:06 am Post subject: Having difficulty with HTTPInput |
 |
|
Centurion
Joined: 16 Aug 2005
Posts: 114
Location: Burlington, NC USA
|
We see the connection to port 7080 and the message is in SYSTEM.BROKER.WS.INPUT, but there is no activity from the message flow. Then message flow consists of the HTTPInput node wired to a trace node wired to a compute node wired to the HTTPReply node. The HTTPINpute node catch terminal has a trace node and throw node wired and the failure node has a trace node wired.
Current Software
AIX 5.2
MQSeries V5.3, CSD9
WBIMB v5.0 CSD 5 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 16, 2005 5:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So, you configured the broker to use port 7080 as the HttpListener port.
You see that biphttplistener is running.
netstat shows that port 7080 is LISTENING.
You have deployed the flow with the HTTPInput node, and the broker reports that the flow is running.
You post an HTTP request to port 7080, using the path that you configured in the HTTPInput node.
And nothing shows up in your traces?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wraymore |
| Posted: Tue Aug 16, 2005 5:37 am Post subject: |
|
|
Centurion
Joined: 16 Aug 2005
Posts: 114
Location: Burlington, NC USA
|
| jefflowrey wrote: |
So, you configured the broker to use port 7080 as the HttpListener port.
You see that biphttplistener is running.
netstat shows that port 7080 is LISTENING.
You have deployed the flow with the HTTPInput node, and the broker reports that the flow is running.
You post an HTTP request to port 7080, using the path that you configured in the HTTPInput node.
And nothing shows up in your traces? |
That is correct and the request sender is timing out |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 16, 2005 5:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Enable broker tracing.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Aug 16, 2005 7:26 am Post subject: Re: Having difficulty with HTTPInput |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| wraymore wrote: |
| We see the connection to port 7080 and the message is in SYSTEM.BROKER.WS.INPUT, but there is no activity from the message flow. |
Can I ask a dumb question? Where is the HTTPInput supposed to get its request from? Is there a second message flow that is using the SYSTEM.BROKER.WS.INPUT queue that issues the HTTPRequest to your second flow? I just set this up on my system with two message flows and everything worked fine. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 16, 2005 7:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I believe that the HTTPListener uses SYSTEM.BROKER.WS.INPUT to communicate with the HTTPInput node.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
