| Author |
Message
|
| jfry |
 Posted: Wed Apr 02, 2008 12:25 pm Post subject: URL for HTTP Input flow |
 |
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
I have created a basic flow that has an HTTP Input node that connects to a Trace node. The trace node then goes on to other nodes. I have the trace node configured to write the Root info to C:\wmb.txt. I am trying to run this flow from a browser but am not getting any trace log. I'm not sure if I am using the correct URL in the browser. I am attempting to go to http://localhost:7080/Test/Trace. My HTTP Input node path suffix is set to /Test/Trace.
Thanks. |
|
| Back to top |
|
 |
| marcin.kasinski |
| Posted: Wed Apr 02, 2008 12:51 pm Post subject: Re: URL for HTTP Input flow |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
A few hints:
- check if flow is running
- try telnet localhost 7080
- connect another trace to failure terminal of HTTPInput
- set flow trace
-...
Another thing :" from a browser" ?
What is input for this Flow, HTTP GET method with parameters in query string ?
_________________
Marcin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 02, 2008 12:53 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also...
Restart your broker twice, and then try again...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jfry |
| Posted: Wed Apr 02, 2008 12:58 pm Post subject: |
|
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
OK....I have restarted my broker twice and no luck. When I try to telnet to localhost 7080, I get the following:
C:\>telnet localhost 7080
Connecting To localhost...Could not open connection to the host, on port 7080: Connect failed
What would cause that to fail.
Sorry if I am asking silly questions. I am very new to all of this.
Thanks again. |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Wed Apr 02, 2008 1:01 pm Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
Is your flow running ?
Is your broker running ?
Any firewall (local or something else) ?
_________________
Marcin |
|
| Back to top |
|
|
| jfry |
| Posted: Wed Apr 02, 2008 1:08 pm Post subject: |
|
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
| My broker and my flow are both running. There shouldn't be any firewall issues. |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Wed Apr 02, 2008 1:13 pm Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| jfry wrote: |
| My broker and my flow are both running. There shouldn't be any firewall issues. |
| jefflowrey wrote: |
Also...
Restart your broker twice, and then try again... |
Have you done it ?
Check HTTP port
mqsireportproperties BROKER_NAME -b httplistener -o HTTPConnector -n port
Is you broker running on localhost ?
Try with HTTP Input node path suffix is set to http://localhost:7080/Test/Trace (if local requests)
_________________
Marcin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 02, 2008 1:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, the path should be "/Test/Trace" on the HTTPInput node. The "http://localhost:7080" is always determined by the HTTP Listener port.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mrgate |
| Posted: Wed Apr 02, 2008 1:19 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| jefflowrey wrote: |
Also...
Restart your broker twice, and then try again... |
Jeoff, why to restart the broker twice.
Hello jfry can you issue command
mqsireportproperties <broker name> -b httplistener -o HTTPConnecto
r -n port
and check whether broker is listening on port number 7080
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 02, 2008 1:20 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mrgate wrote: |
| Jeff, why to restart the broker twice. |
...
because.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jfry |
| Posted: Wed Apr 02, 2008 1:20 pm Post subject: |
|
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
Here is what I get from that report command:
d:\IBM\MQSI\6.0>mqsireportproperties Local_Broker -b httplistener -o HTTPConnect
or -n port
7080
BIP8071I: Successful command completion.
My broker is running locally on my PC so I would assume it is running on localhost. |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Wed Apr 02, 2008 1:26 pm Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| jefflowrey wrote: |
No, the path should be "/Test/Trace" on the HTTPInput node. The "http://localhost:7080" is always determined by the HTTP Listener port. |
I know , but I remember that long time ago I tested broker on Win with localhost requests and I had some problems with short suffix (without full URL).
I could be totally different problem but it is always better to check.
_________________
Marcin |
|
| Back to top |
|
|
| jfry |
| Posted: Wed Apr 02, 2008 1:32 pm Post subject: |
|
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
Try with HTTP Input node path suffix is set to http://localhost:7080/Test/Trace (if local requests)
I tried this with same results. I have changed it back to /Test/Trace |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Apr 02, 2008 2:42 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
If you cannot telnet to the port, then either you are blocked by a firewall or the broker is not listening. To determine this you can issue "netstat -a" to see if the listener is listening. Also, the broker issues a message to the event/sys log to say when it starts listening (and on what port). Do you see this message?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| mrgate |
| Posted: Wed Apr 02, 2008 3:18 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| mgk wrote: |
| I can cannot telnet to the port, then either you are blocked by a firewall or the broker is not listening. To determine this you can issue "netstat -a" to see if the listener is listening. |
from the reslut of mqsireport command, we can clearly see that broker is listening on port.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
|
|
