| Author |
Message
|
| DBN-GUY |
 Posted: Tue Apr 24, 2007 6:56 am Post subject: Broker not catching HTTPrequest timeout |
 |
|
Newbie
Joined: 26 Jul 2006
Posts: 6
Location: South Africa
|
Hi
I am currently using Message Broker 6 with fix 6.0.2.
I am doing a httprequest to another webservice(written in .net) from another company. The problem that I am experiencing is that when the other company's service is down I do not get an error back(not expected since their service is down) but more importantly I do not get a timeout error or a response saying that the message has timeout.
Has anyone come across this before and how did you handle this situation if no error/reponse is thrown.
Is this something that IBM has overlooked 
Thanks in advance for your response |
|
| Back to top |
|
 |
| mgk |
| Posted: Tue Apr 24, 2007 7:23 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
You should get an exception if the Request node timesout. By default the timeout is 3 minutes, did you wait long enough? Also have you got any failure / catch terminals wired up that could be swallowing the exception?
_________________
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 |
|
|
| DBN-GUY |
| Posted: Tue Apr 24, 2007 10:19 pm Post subject: |
|
|
Newbie
Joined: 26 Jul 2006
Posts: 6
Location: South Africa
|
Thanks for the response.
I have changed the timeout to 45 seconds. The failure/catch terminals are not wired anymore so it should be doing a role back and writing the failure to the DLQ.
Usually when the Host service does not reply timeously I do get a timeout message. If the host service is stopped for maintainace then I do not get any timeout response.
Also I have tried to run a debug trace and I also wired the failure and catch terminals with a trace node. All I see here is broker does the HttpRequest and thereafter there is nothing, broker just starts with the next message and nothing happens.!!!!!! |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Apr 25, 2007 3:37 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Can you post your flow details here, along with the settings on each node?
_________________
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 |
|
|
| DBN-GUY |
| Posted: Wed Apr 25, 2007 3:54 am Post subject: |
|
|
Newbie
Joined: 26 Jul 2006
Posts: 6
Location: South Africa
|
I have the following flow,
MQinput >> Compute >> HTTPRequest
I am using default properties the only different property in the HTTPrequest is the timeout = 45 seconds.
The problem that I am experiencing, is it because when the destination service is down, the message is going via the internet, and at that point in time the Host service no longer exists so the message travels indefinetly across the internet until it dies.
But that still does not explain why my request does not timeout.
Any thoughts here |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Apr 25, 2007 5:11 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Well I could wire is as:
MQinput >> Compute >> HTTPRequest[out and error terminals] >> TraceNode[trace $Root and $LocalEnvrionment and $ExceptionList] >> File
And post anything in the File here. Have you checked the event log / syslog as well?
Also what version of the product (including CSDs are you using)?
_________________
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 |
|
|
| ashoon |
| Posted: Wed Apr 25, 2007 6:15 am Post subject: just a thought |
|
|
Master
Joined: 26 Oct 2004
Posts: 235
|
I've found many companies looking at HTTP transports to move business critical data... might I suggest that you consider MQ as the transport which would easily solve this problem...
remember web-services (SOAP data) is transport independent. |
|
| Back to top |
|
|
|
|
