Skip to Content
0
Former Member
Aug 01, 2016 at 09:35 AM

AS2 receiver adapter throwing bad_certificate # error after certificate renewal

114 Views

Hi All,

PI 7.1

Seeburger AS2 adapter.

We are using Seeburger AS2 receiver adapter, running SAP PI 7.1 to communicate with external trading partner. This interface is working fine, until certificate is renewed. After the certificate renewal it's started throwing the following error. Error occurs during the SSL Handshake.

Error: Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #

Error: MP: exception caught with cause javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #

Error: Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #

Error: Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # .

I have gone all the other discussion on this issue on SCN.

My trading partner has confirmed that certificates are stored in TrustedCAs. I have also restarted our PI server.

Any ideas please?

Thanks in advance.

Vijay