on 09-24-2016 8:53 AM
Dear Experts,
We are having B2B scenarios. ECC <--> SAP PO <--> Bank
Sender Adapter : RFC
Receiver Adapter : HTTP_AAE
PO Version : 7.4 SP13
While trying with test message we are getting following exception.
Exception caught by adapter framework: ERROR_SENDING_HTTP_REQUEST-Message Processing Failed. Reason : java.net.ConnectException: errno: 110 (Connection timed out), error: Connection timed out .
Transmitting the message using connection AFW failed, due to: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SENDING_HTTP_REQUEST-Message Processing Failed. Reason : java.net.ConnectException: errno: 110 (Connection timed out), error: Connection timed out (local port ******* to address 0:0:0:0:0:0:0:0, remote port 443 to address ***************)
N/w team stating F/w has already been opened.
Request your kind inputs on this.
Best Regards,
Suresh S
Hi Raghu and Praveen,
We are trying to hit HTTPS url (B2B) Integration from PI Server.
I have below configuration in my communication channel.
We have generated CSR request (against one private key) and gave it to Bank for Certificate Signing.
Bank returned the Public certificate and also Root and Shared certificate.
We have imported those certificate as CSR Response (inside Trusted CAs) . Now we are facing this issue.
Attached above the HTTP_AAE Adapter screenshot. Do we need to use specify client certificate also? Please confirm.
Best Regards,
Suresh S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh,
You can call the web service with client certificate or without certificate, it is dependent on web service side configuration. Ask them are they accepting without client certificate, if yes current configuration is right. Make sure the root certificate imported into TrustedCA in NWA, check below blog for more details.
Regards,
Praveen.
Hi Suresh,
This is because of timeout occurred in receiver web service application side and PI show the same in the log.
Check section 2.8 in below document.
Potential cause for the error:
- It is a tricky error which occurs due to timeout on third party system.
- Failure happens while calling the receiver application.
- Generally the web server on receiver side throws the time out error which PI captures and displays in Messaging System.
You can configure the TraceHTTP parameter in receiver HTTP_AAE adapter then you can see the request and response.
Regards,
Praveen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Suresh,
Try hitting the WS using soap UI or other tools and see the time taken to get the response back, This could be due to problem where response is not received with in the timeout parameter.
Check the below discussions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.