Skip to Content

Adapter Module migration to 711

Hi,

  we recently update SAP PI to & 711 and I had to migrate the custom module adapter! I performed all steps necessary but when I deploy the EAR file I get a warning:

1. Exception has been returned while the [sap.com/EPA_NewDias_EAR] was starting. Warning/Exception :[

][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/EPA_NewDias_EAR].]

And in the communication channel I get an error:

  Error:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception
during lookup operation of object with name
localejbs/DiasParseFile_DXreosis_NEW, cannot resolve object reference. [Root
exception is javax.naming.NamingException: Error occurs while the EJB Object
Factory trying to resolve JNDI reference Reference Class Name: Type:
clientAppName Content: sap.com/EPA_NewDias_EAR Type: interfaceType Content:
local Type: ejb-link Content: DiasParseFile_DXreosis_NEW Type: jndi-name
Content: DiasParseFile_DXreosis_NEW Type: local-home Content:
com.sap.aii.af.lib.mp.module.ModuleLocalHome Type: local Content:
com.sap.aii.af.lib.mp.module.ModuleLocal
com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException:
Cannot start applicationsap.com/EPA_NewDias_EAR; nested exception is:
java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting
application locally and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE
DPL.DS.5029] Exception in operation [startApp] with application
[sap.com/EPA_NewDias_EAR]. at
com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)
at
com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:144)
at
com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:63)
at
com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:77)
at
com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33)
at
com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:228)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283) at
com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:434)
at
com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:223)
at
com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:242)
at javax.naming.InitialContext.lookup(InitialContext.java:351) at
javax.naming.InitialContext.lookup(InitialContext.java:351) at
com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:69)
at
com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:50)
at
com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.getModuleLocal(ModuleProcessorBean.java:419)
at
com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287)
at sun.reflect.GeneratedMethodAccessor319.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592) at
com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:74)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy258.process(Unknown Source) at
com.sap.aii.adapter.file.File2XI.send(File2XI.java:3519) at
com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1345) at
com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:630) at
com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:534) at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
java.security.AccessController.doPrivileged(Native Method) at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280)
]

----------------------------------------------------

In the reference in application-j2ee-engine.xml I have:

-------------------------------------------------

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

<application-j2ee-engine  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">

<reference reference-type="hard">

<reference-target provider-name="sap.com" target-type="service">engine.security.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target provider-name="sap.com" target-type="library">engine.j2ee14.facade</reference-target>

</reference>
<reference reference-type="hard">

  <reference-target provider-name="sap.com" target-type="service">com.sap.aii.af.svc.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target provider-name="sap.com" target-type="interface">com.sap.aii.af.ifc.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.lib.facade</reference-target>

</reference>

<reference reference-type="hard">

   <reference-target  provider-name="sap.com" target-type="library">com.sap.base.technology.facade</reference-target>

</reference>

<fail-over-enable mode="disable" xsi:type="fail-over-enableType_disable"/>

</application-j2ee-engine>

---------------------------------------------------------------

And in ejb-j2ee-engine.xml the jndi names are correct (same in Communication channel)

------------------------------------

...

<enterprise-bean>

   <ejb-name>DiasParseFile_DXreosis_NEW</ejb-name>

   <jndi-name>DiasParseFile_DXreosis_NEW</jndi-name>

</enterprise-bean>

...

-----------------------------------

and in ejb-jar.xml

--------------------------------

       

<session>

            <icon/>

            <ejb-name>DiasParseFile_DXreosis_NEW</ejb-name>

            <home>com.sap.aii.af.lib.mp.module.ModuleHome</home>

            <remote>com.sap.aii.af.lib.mp.module.ModuleRemote</remote>

            <local-home>com.sap.aii.af.lib.mp.module.ModuleLocalHome</local-home>

            <local>com.sap.aii.af.lib.mp.module.ModuleLocal</local>

            <ejb-class>com.sap.adaptermodule.DiasParseFile_DXreosis_NEWBean</ejb-class>

            <session-type>Stateless</session-type>

            <transaction-type>Container</transaction-type>

</session>

---------------------------------

Any Ideas?

Thanks,

S.Socratous

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 19, 2013 at 06:46 AM

    Socrates,

    Did you ever resolve this issue?  If so, could you provide any hints on what the problem was.  I am having the exact same issue on a PI 711 system.  I don't seem to have the issue with Adapter Module developments on a PI 700 or 731 systems.

    Thanks,

    Jason

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Note I have resolved this error.  The cause was the deployed SDA including a jar file containing code compiled on java 1.6.  I rebuilt the library using java 1.5 and then redeployed the adapter and all is good.

      Note the error message given was a lot clearer when deploying through NWDS (gave meaningful error at deployment) rather than deploying through SDA (only gave error when executing adapter module).

      Regards,

      Jason