Skip to Content
0

REST Adapter -> RoutingException: InterfaceDetermination did not yield any actual interface

Aug 29, 2017 at 08:04 PM

183

avatar image

I am having a problem with a REST adapter. It is setup with the following configuration:

I have triple checked to make sure the XSD generated matches the data being sent including the SIOS name wrapper, but I keep getting the following error:

Error in message processing
[EXCEPTION]
com.sap.aii.adapter.rest.ejb.sender.ModuleProcessorException: Error while sending message to module processor: Sender Channel 'CC_REST_SND_Hybris' (ID: 5f29f02388a63e7c80a3fd6ad4407fdd): Catching exception calling messaging system: InterfaceDetermination did not yield any actual interface
at com.sap.aii.adapter.rest.ejb.sender.RESTSenderChannel.service(RESTSenderChannel.java:349)
at com.sap.aii.adapter.rest.ejb.RESTAdapter.service(RESTAdapter.java:137)
at com.sap.aii.adapter.rest.web.RESTServlet.service(RESTServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

...

The log for this message shows the following:

I really need help understanding why the REST Adapter cannot find the Interface determination. I have compared the resulting XML conversion to the XSD Schema and they match. The OM map (via test) works with the XML as it was converted.

I have deleted and recreated the Integrated configuration objects. Made updates to force a cache refresh. Everything I can think of but nothing seems to allow this to work.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

avatar image
Former Member Aug 30, 2017 at 05:39 AM
0

Can you check if Interface Name, Namespace and SWC of message from Rest Adapter is exactly matching with what you have configured?

Thanks,

Sunil

Show 1 Share
10 |10000 characters needed characters left characters exceeded

I have checked, re-created, etc... I cannot find a real difference to cause the problem. I actually did get it to work for a few days then we did further testing and now it doesn't work again.

0