IBM Integration Bus SOAP service Invoke error

I have designed a message flow with IIB by using the following component

HttpInput(REST) - ESQLComputeNode - SOAP Request - ESQLComputeNode2 - HTTPReply

I have exposed a REST service from this application to invoke by the user and then based on the user's input I build the SOAP message and request it through the SOAP request node,

But when the message reached to SOAPRequest node it always gives me Socket Timeout Exception,

  1. SOAP service can be invoked successfully with SoapUI or POSTMAN with the same network connectivity.
  2. I have checked the accuracy of the endpoint so many times and I can assure you that there is no such issue on that.

3. However, that SOAP URL cannot be resolved by the browser and it always gives me "The Site cannot be reached "

  1. I tried the tracert and telneting the destination and it works fine ,
  2. I have imported the WSDL into my workspace and the message is developed based on that wsdl's namespaces.
  3. I have obtained the generated message before invoking the web service on IIB and tried that message on SOAPui and it still works fine.
  4. I have tried by changing the SOAPrequest's operation mode to "Invoke a generic web service " and still unable to connect and gives the same socket timeout exception.

I have been struggling with this issue for a month and can anyone find a solution for me to get rid of this annoying error.

I am in a doubt that this could occur due to the 3rd point I have mentioned above, but still it works fine with SoapUI and POSTMAN.

Upvotes: 0

Views: 1572

Answers (2)

Removing soap envelope from the request message and it resolves the issue.

Upvotes: 0

kimbert
kimbert

Reputation: 2422

It sounds very much like a network configuration problem. I would

If necessary, perform the curl command while the network team do a trace to find out where it is getting blocked.

Upvotes: 0

Related Questions