Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Strange Lookup Error (SAP Resource Adapter)

Hi all,

I received a quite stange error (Below you can see the relavent part of the logfile).

While the first attempt to get the ConnectionFactory of the SAP JRA succeeds, the second one fails. As you can see, context and parameters of the lookup are exactly the same. Does anybody has experiences with this problem?

Thanks a lot

Nadine

*******************************************************

<b>1st attempt</b>

DEBUG SAPEngine_Application_Thread[impl:3]_18 com.xxx.ik.ejb.srouter.util.SystemRouterUtil - return jca

name: java:comp/env/SAPJCA

INFO SAPEngine_Application_Thread[impl:3]_18 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO - search for

JCA Adapter: java:comp/env/SAPJCA

DEBUG SAPEngine_Application_Thread[impl:3]_18 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO -

connectionfactory: com.sap.mw.jco.jra.JRA$ConnectionFactoryImpl@1d4445d

<b>2nd attempt</b>

DEBUG SAPEngine_Application_Thread[impl:3]_1 com.xxx.ik.ejb.srouter.util.SystemRouterUtil - return jca

name: java:comp/env/SAPJCA

INFO SAPEngine_Application_Thread[impl:3]_1 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO - search for JCA Adapter: java:comp/env/SAPJCA

ERROR SAPEngine_Application_Thread[impl:3]_1 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO -

com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/SAPJCA.

Former Member
replied

Hi Nadine,

Yes, this exactly causes the problem. The resource SAPJCA is available in SAPGenericEJB's environment and the lookup succeeds since it is performed on behalf of that EJB. What is this workflow-engine? If it is another EJB or web module, then you have to define the resource-ref in its deployment descriptor too.

Best regards,

Vladimir

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question