how to troubleshoot broken outgoing webservice calls?

Posted by cipdwak on 06-Jan-2011 07:50

Due to some unknown issue, al our outgoing webservice invocation calls are broken:

loggin show only this last entry:

[11/01/06 10:54:02] ID=ESBrsvz (trace) [WSInvocation] Invoking synchronous SOAP request-response callout. Waiting for response...

But we do not recieve a response. Nothing really, no logentry, no error message, nothing in the deadmessage queue. It just disappears into oblivion.

It is not just one webservice call in one process, but multiple calls to different webservices in multiple processes. All these webservices are accessable via a webbrowser on the same machine.

This is on a sonic MQ/ESB 7.5.2 platform.

Does anybody have an idea on where to start troubleshooting this issue?

T.i.a

Koen

Technology Partner - Forum

All Replies

Posted by scott_auge on 08-Jan-2011 17:29

I would obtain SoapUI (there is a free version) and attempt the calls manually. Often, a lot of interesting things will show up, either in bad WSDLs, networking routing/blocking, user account settings, etc.

Posted by tsteinbo on 12-Jan-2011 05:35

Since in 7.5 invocations go via the broker use SMC to turn on tracing for HTTP Direct. You will see the request and response http codes. That should alow you to find out if you get a response back to the broker or not.

An alternative option is to use some form of tcp tunnel and send/receive via the tunnel.

Thomas

This thread is closed