cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP : MessagingException - Adapter Framework caught exception: null

0 Kudos

hi friends,

We use an interface where the sender is SAP system and receiver is SOAP adapter. The receiver SOAP url is a secure connection (https) that uses SSL certificate.

Recently we are getting the following error :

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException

Error Adapter Framework caught exception: null

Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.

We checked the following :

1. The security certificate is in the keystore and is valid.

2. The secure url is also working fine when opened in browser.

Messages were successfully processed in this interface in the past. But for the last one month, all messages have failed with this error. No changes were made to the channel parameters that could be causing this problem.

Could you please help ?

Accepted Solutions (0)

Answers (1)

Answers (1)

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

Messages were successfully processed in this interface in the past. But for the last one month, all messages have failed with this error. No changes were made to the channel parameters that could be causing this problem.

Can you try adding :443 in our URL as https port? We have experienced the same problem in one of our patch upgrades and adding the ports in the URL solved the issue. Probably this could also be true in your case.

Regards,

Mark

0 Kudos

Hi Mark,

Thanks for your suggestion.

We are already using "https://" in our url.

Are you suggesting that we have to include ":443" in the url ? If so, where ?

The url looks like :

"https://<....................>DefaultService?wsdl&mode=ws_policy"

Regards,

Manoj

former_member472138
Active Contributor
0 Kudos

Hello Manoj,

You should check if your SOAP request is reaching your given port. Check the log in nwa and Monitor the channel.

As suggested, you can also give a try while changing the port.

https://hostname:port/DefaultService?wsdl&mode=ws_policy"

Regards

Pothana