on 04-12-2009 10:22 AM
I use abapProxy to invoke an external webservice via SOAP adapter but i get an error "invalid http response: null" in sxmb_moni so i thought that there might be an mistake in request SOAP message and I installed TCPGateway to see logs about sending and coming message.
When i invoke the proxy, sending part of TCPGateway is empty but as you guess , coming part of it shows an error "java.net.ConnectException: Connection timed out : connect"
What maybe the reason for that SOAP adapter sends an empty SOAP message?
Thanks
Hi Abhishek;
As i mentioned , i used TCPGateway program on XI server to see going message to external webservice..this gateway program takes request and forwards it but it still comes as empty SOAP message from XI adapter to this TCPGateway program.
as you guess, when you send empty soap message , external webservice doesnt respond to this request so it gets timeout error.
ps: i tried to invoke this webservice via another third-party tool, it works properly.
What would another reason except firewall settings for this issue ? because i do all of these control on XI server, namely before empty soap message goes.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you see the payload after the message mapping step in sxmb_moni? Then, could you see the payload in message monitor of RWB when you click on details of the particular message?
Check if there was a change in wsdl after you have imported it in XI. And see if soapAction is required or not. You can check soapAction in the wsdl with tagname "soapAction".
Regards,
Prateek
Hi,
java.net.ConnectException: Connection timed out : connect
The reason for this error could be any of the following:
1) XI tried posting the msg to the webservice but the webservice is down.
2) The port through which XI is connecting to the WebService is blocked due to some Firewall settings. Contact your network admin to check if the any Firewall setting is applied that is blocking this communication.
3) The target url which you mentioned in the Receiver SOAP Adapter may be wrong.
Regards,
Abhishek.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.