on 08-07-2014 7:46 PM
Basis recently turned on an old PI box that was used during our initial conversion with the idea we would use this box for some new testing.
After working through a number of issues with the cache and passwords and IDoc adapter, we come to the SOAP receiver which is giving me fits. I have changed the URL to point to the correct ECC box and updated the username and password. Yet, I suffer through these errors, to which I beg for assistance.
07.08.2014 13:45:30 Information The message was successfully retrieved from the send queue.
07.08.2014 13:45:30 Information The message status was set to DLNG.
07.08.2014 13:45:30 Information Executing request mapping "urn:xxxxxx-net:P2P-055I:XXXXXDailyPriceFile/DardenDailyPFS_To_XXXXXXDailyPF_OM"
07.08.2014 13:46:26 Information Delivering to channel: SOAPReceiver_Common
07.08.2014 13:46:26 Information SOAP: request message entering the adapter with user J2EE_GUEST
07.08.2014 13:46:27 Error SOAP: call failed: java.net.ConnectException: Connection refused: connect
07.08.2014 13:46:27 Information SOAP: sending a delivery error ack ...
07.08.2014 13:46:27 Information SOAP: sent a delivery error ack
07.08.2014 13:46:27 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
07.08.2014 13:46:27 Error Adapter Framework caught exception: java.net.ConnectException: Connection refused: connect
07.08.2014 13:46:27 Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect.
07.08.2014 13:46:27 Error The message status was set to NDLV.
If anyone has a suggestion to fix, or how I can see more details on this error, much appreciation would follow.
Hi Dave
Error clearly shows there is a connection problem. There can be many reasons for the connection issue.
Please check all these points, if everything is fine.
- Client and Server, either or both of them are not in network.
- Server is not running
- Server is running but not listening on port, client is trying to connect.
- Firewall is not permitted for host-port combination
- Host Port combination is incorrect.
- Incorrect protocol in Connection String
- Open the webservice link(in soap channel) in any browser and see if you are able to access it.
Regards
Osman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dave,
Most of the times it will be firewall. log into your pi system on os level and do telnet to target system with correct port. basis team can help you on this.
Regards,
Muni.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.