| Author |
Message
|
| Plons |
 Posted: Fri Jan 26, 2007 6:41 am Post subject: HTTPinput not listening to URL |
 |
|
Newbie
Joined: 26 Jan 2007
Posts: 6
|
Hi,
I'm new to WMB and I'm trying to get the httpinput node to work.
I've got a flow: HttpInput->ComputeNode->MQOutput
I've got it working for http://localhost:7080. However it is ONLY working for localhost:7080 
Even if I replace the URL from / to /service (or /service/ or service or /* or /wathever) it still keeps working for localhost:7080, but for all other url's i try with nettool or my webbrowser I get the message that there's no message flow for that URI, although it is set in the URL of the httpinput.
I've restarted the broker several times (as mentioned in another post), but no effect...
Any idea's
Thx in advance
Plons |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jan 26, 2007 6:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
1) Change your HTTPInput node properties to specify the new URL you want - this should ONLY be the part that would follow "http://localhost:7080".
2) Update the contents of your BAR file.
3) Redeploy the Bar file.
4) Confirm that the deployment was successful.
5) Restart the broker TWICE.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Plons |
| Posted: Fri Jan 26, 2007 7:37 am Post subject: |
|
|
Newbie
Joined: 26 Jan 2007
Posts: 6
|
Thx for the quick reply.
I've found where the problem lies. I had a Message set attached to the HttpInput. It seems that was causing the strange behaviour. It wasn't enough to just clear the message set from the httpinput-properties screen. I had to remove it also from the execution group. When I did that, it worked.
i'll now try to figure out what could be wrong with the messageset.
If you got any ideas i'll be glad to hear them. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 26, 2007 7:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There's no way any association of a message set to an HTTPInput node will cause the URL to fail to be recognized, unless you are doing something very strange to associate the message set with the HTTPInput node.
Or if it was causing your Deployment to fail. So the deployed flow wasn't getting updated to use the new URLs.
That's why I made sure to include #4 in my list of steps.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| KBA |
| Posted: Fri Jan 26, 2007 12:34 pm Post subject: |
|
|
Newbie
Joined: 29 Nov 2006
Posts: 7
|
follow the bellow
In ur HttpInput Node Url selector = /Service/*
From ur net Tool give the url http://localhost:7080/Service
This should wrk once enter to this node u may get error if u have problem with ur message set.
Can i know the error about ur message set? |
|
| Back to top |
|
|
|
|
