Exception in getMethodReady() for stateless bean

[former_member191528]

Hello All,

We were getting the following errors for all our scenarios using the JDBC adapter. It started early morning and both our synchronous and asynchronous scenarios which use the JDBC adapter were failing with the error message shown below. Can anyone provide some more insight into what caused this error. We had to restart the server node to resolve this issue.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Inbound Message

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.af.appxml|com.sap.aii.af.ejb.jarxml|CallAdapterWithMessageBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.af.app.modules.CallAdapterWithMessageBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.af.app.modules.CallAdapterWithMessageBean@759577ed for bean sap.com/com.sap.aii.af.appxml|com.sap.aii.af.ejb.jarxml|CallAdapterWithMessageBean; nested exception is: javax.ejb.CreateException: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SapXIFileAdapterService.</SAP:AdditionalText>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Thanks.

Kiran

[prateek · Accepted solution]

The problem seems to be related to the Adapter Engine but not sure about the exact reason. As per the last line of the log, either the channel reference was missing or there was some problem with the related service which could be viewed in visual admin. This could have occurred when the channel is initialized for the use. Restart helped because it may have restarted the related services.

Regards,

Prateek