Object not found in lookup
Hi! This is my first post!
After patching the portal from NW7.0 SP16 to NW7.01 SP4 (EHP1), strange erros appear frequently in the traces.
I'm not able to determine them. (I don't want to post the hole trace. Is there a way to attach it?)
"Bean SALS_MTE_GET_BY_TOOL_RUNSTATUS not found on host nsiko01, ProgId=nsiko01.sapccmsr.09: Object not found in lookup of SALS_MTE_GET_BY_TOOL_RUNSTATUS.registered entries for FuctionName=JNDIName : {GET_AWF_LOCALIZED_STRING=PRTRFC_BASE, GET_AWF_SUBPROC_LOG_DATA=PRTRFC_BASE, RSWR_ZIP_STREAM_GET=PRTRFC_BASE, SALV_WD_EXPORT_PDF=PRTRFC_BASE, RSWR_SYSTEM_ALIAS_CHECK_PROXY=PRTRFC_BASE, RSRD_X_MAP_TO_PRTL_USERS_PROXY=PRTRFC_BASE, RSPOR_SHORT_TO_URL_CONVERT=PRTRFC_BASE, CPETEST=PRTRFC_BASE, LSO_COL_GET_TEMPLATES=PRTRFC_BASE, RSWR_SAP_ROOT_FOLDER_GET=PRTRFC_BASE, LSO_COL_GET_EXT_ROOMACCESSURL=PRTRFC_BASE, RSRD_GET_PORTAL_USERS=PRTRFC_BASE, CREATE_AWF_TASK=PRTRFC_BASE, CANCEL_AWF_SUBPROCESS=PRTRFC_BASE, ..."
Thanks in advance!
Erwin
hi Erwin,
based on the u r error messages, i found in google(this error message "RSWR_SAP_ROOT_FOLDER_GET") this may be error with bi-java error
for more clarifications u can refer this following links
Error while setting up BI and EP
let me know am i correct or not
ravindra
Similar Messages
-
PI 7.0 JMS Rcv Adapter: Object not found in lookup of XIJMSService
Hi all,
When sending messages to an JMS queue, JNDI setup, in the Message Monitoring we get the error:
"MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of XIJMSService.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of XIJMSService."
The Error points to the Module Processor. Indeed the 2 default Modules are used:
- SAP XI JMS Adapter/ConvertMessageToBinary
- SAP XI JMS Adapter/SendBinarytoXIJMSService
This second Module contains 'XIJMSService', and according the documentation (http://help.sap.com/saphelp_nw04/Helpdata/EN/4d/a3bc97ff55c742af7faed661635baf/content.htm)
, it uses a parameter named 'modulePoolAdminLookupName' with the default value: /XIJMSService.
This is how far we get. Even when we assign a different value to the parameter 'modulePoolAdminLookupName' , the error in the Message Monitoring stays the same.
Has anyone experience with this issue, or any ideas to investigate or solve this?
Thanx in advance, Walter.Hi all,
Issue is solved. Apparently the Java-version on our XI-server (1.4.2) could not handle the Vendor's JMS-driver we installed (ActiveMQ 4.1.2.jar) so we tried using the ActiveMQ 4.1.0.jar as the JMS-driver. Now it is OK and message are put on the destination queue.
Walter. -
Hi AS2 experts,
*When i tried sending an xml to partner system using AS2 adapter.. Mapping is succesfull and message is failing in receiver AS2 adapter.
1. I used the following parameters in AS2 Module.
ModuleName Module Key
localejbs/Seeburger/solution/as2 solutionid
localejbs/ModuleProcessorExitBean exit
ModuleKey ParameterName ParameterValue
exit JNDIName deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Iam getting the following error.
Success MP: Processing local module localejbs/Seeburger/solution/as2
Error : MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2.
Error : Exception caught by adapter framework: Object not found in lookup of as2.
Error : Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of as2.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of as2..
2. When i tried by removing Modulename "localejbs/Seeburger/solution/as2"
It is showing the below error like AS2ID is missing.. but its there in party configuration.
Error :
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Can anyone has idea what might be wrong.
Kindly suggest me asap.
Thank You.
Regards
Seema.Hi,
Plesae go through below links
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
and
Check with below configuration
Configuration for AS2 or simple file adapter.
We are using this module configuration for converting EDI D96A format to XML:
1 localejbs/CallBicXIRaBean Local Enterprise Bean bic
2 localejbs/CallSapAdapter Local Enterprise Bean 0
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic logAttID ConverterLog
bic mappingName See_E2X_ORDERS_UN_D96A
bic saveSourceMsg ORIGINAL_EDI
can someone please tell me the module configuration for reverse mapping at receiver end,i.e.,XML to EDI D96A
basically,I need mapping name for this.
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
File receiver:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_X2E_EDIFACT_ORDERS_UN_D93A
ONly the mapping program name changes from E2X to X2E. IN ur case it will be See_X2E_ORDERS_UN_D96A
Thanks
Swarup -
XI--- OpenJMS error Object not found in lookup of XIJMSService
Hi all,
I am trying XI-->OpenJms (Server).
I have included openJms.jar library in aii_af_jmsproviderlib.sda and deployed using SDM.
In JMS receiver adapter I am using the following Configuration:
Transport protocol: JMS Provider with JNDI .
Queue connection factory : org.exolab.jms.client.JmsConnectionFactory
JNDI-Name JMSQueue: org.exolab.jms.client.JmsQueue
Context Factory : org.exolab.jms.jndi.InitialContextFactory
JNDI-Server adress :tcp://10.1.102.5:3035
In RWB i am getting the following for this scenario:
Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.
Kindly help what other configurations are required.
Best Regards,
LemineHi Sebastian,
I have still the same problem.
could you send me a screen shot with your configuration?
(openjms configuration).
my email: [email protected]
I have the following standard configuration in my modul:
Verarbeitungssequenz:
Modulname: Type:
ocalejbs/SAP XI JMS Adapter/ConvertMessageToBinary L
localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService L
could that cause for that prblem ?
Thanks for helpful answer.
best regars.
Lemine. -
XI error: Object not found in lookup of RfcAFBean
Hi Forum,
In a scenario, I have a BPM, which makes a synchronous call to R/3 for execution of a rfc enabled Function module, while doing so, it gives an error as a response, which i can see in the MONI:
<b>com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of RfcAFBean</b>
what can be the reason for the error? and how can it be avoided?
pls helpit might be a cache problem, run the CPA cache and check.
ir, id cache the data here also. -
WebDynpro app stopped working (Object not found in lookup of JPA_DEFAULT)
Hi,
my scenario is as as described in my posting (java.lang.IllegalArgumentException: model object must not be null). after i got everything up and working it suddenly stopped.
the wedynpro project is implicitly stopped, beacuse earecipe could not start, reason:
[code]
Error occurred on server 15129750 during startApp demo.sap.com/earecipe : com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:582)
at... [see details]
Error occurred on server 15129750 during startApp demo.sap.com/earecipe : com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:582)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:277)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:246)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:151)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:81)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:480)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:537)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:149)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$2.run(ParallelAdapter.java:350)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:130)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:226)
[/code]
whats that supposed to mean, i'm not using any JPA functionality at the moment.
regards,
christianHi,
you have to define a datasource alias for your db (in "Application Resources" in SAP Netweaver Administrator) or use an existing one and add it as a "jta-data-source" child for your corresponding persistence unit within your persistence.xml
regards,
christian -
ERROR:NameNotFoundException: Object not found in lookup of MYDB
NW 7.0 SP3
I have defined a datasource MYDB by VA,and it tests OK.
I wonder about how to use it in J2EE project or in WebDynpro Project.
I created a J2EE project ,in the Web Model ,i new a class Test:
public static Connection myconn(){
Context ctx = new InitialContext();
Connection conn = null;
DataSource dataSource = null;
dataSource = (DataSource) ctx.lookup("MYDB");
conn = dataSource.getConnection();
return conn;
then in webcontent ,I new a JSP page:
<%
Connection conn = com.Test.myconn();
java.sql.Statement st = conn.createStatement();
String str = "select * from TMP_NAME";
ResultSet rs = st.executeQuery(str);
rs.next();
String str1 = rs.getString(1);
%>
after build and deploy the *.ear,the server returns an error:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of MYDB.
Now I do not know anything else should I do,such as create a reference,and so on.
Thanks for you all help!Hi,
Try the code as below:
DataSource ds = (DataSource) context.lookup("java:comp/env/jdbc/MYDB")
Go through the below help link:
http://help.sap.com/saphelp_nw2004s/helpdata/en/82/fdbf2085f65f43a71e755fc904478d/content.htm
Go through the below thread for more info:
Re: datasource using VA
Regards,
Charan -
NameNotFoundException: Object not found in lookup of FilenameModuleBean
Hello,
after migration from XI 3.0 to PI 7.10 we have a problem with a Java-Module in the File-Adapter.
In XI 3.0 we hat only a EAR-File. We converted it into a SCA-File an deploy it with the JSPM.
I also can see the Objekt in the JNDI-Browser under:
localejbs/sap.com/fnmodear/FilenameModuleBean
rfcaccessejb/sap.com/fnmodear/FilenameModuleBean
sap.com/fnmodear/FilenameModuleBean
ejbCosNaming/sap.com/fnmodear/FilenameModuleBean
but not under:
AF_Modules/ (I don´t know if it matters)
In the File-Adapter we try FilenameModuleBean in the Module Name, but we get the following error message:
18.11.2010 17:02:59 Fehler Adapter Framework caught exception: Object not found in lookup of FilenameModuleBean.
18.11.2010 17:02:59 Fehler Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of FilenameModuleBean..
It seems that he can´t look up the JNDI name.
I hope anyone can help me with the problem.
Best Regards
Georg
Edited by: Georg Kunkel on Nov 18, 2010 5:21 PMHi Georg,
I believe the java module "FilenameModuleBean" in your case is a custom adapter module and hence it would not be available under AF_Modules. The AF_Module is for the modules which are shipped with PI by SAP like PayloadSwapBean, XMLConvertorBean etc.
As a checklist, please check the following entries in the module tab of the channel configuration:
1. Module Name: FilenameModuleBean
2. Type: Local Enterprise Bean
3. Module Key: Any Constant Value
4. Module parameters for this module key (Necessary only if the custom module expects any inputs)
Also as you mentioned,
>>In XI 3.0 we hat only a EAR-File. We converted it into a SCA-File an deploy it with the JSPM.
For this, there might be a case that the .SCA file was not generated properly. To properly generate the .SCA or .SDA file you can:
1. Build sca from ear using nwpacktool described in SAP note:1223957
2. Use NWDS 7.1. You can convert your EAR file to SDA file with the help of CECTL & nwcetool provided with NWDS 7.1
Check: Re: How to build an adapter module in NWDS 7.1?
You might also want to look at the following link for creating custom adapter module for PI 7.10
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa?quicklink=index&overridelayout=true
In case everything looks fine to you, a manual re-start (if possible) of the PI Server should solve the problem.
I hope this helps.
Regards, Gaurav. -
Object not found in lookup of XMLAnonymizerBean..
I have followed the Blog here, from Stefan (excellent, by the way!)
/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean
i have the following xml.....
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Message xmlns:ns0="http://www.host.com/aoc">
<ns0:header>
<ns0:trackingId>00237DA659FD1DDF8CA4B49A1800AC7E</ns0:trackingId>
<ns0:msgClass>PUBLISH</ns0:msgClass>
<ns0:msgName>MX001</ns0:msgName>
<ns0:owner>SAPECD</ns0:owner>
<ns0:version>1</ns0:version>
<ns0:timestamp>2010-03-16T17:59:21Z</ns0:timestamp>
</ns0:header>
i am trying to strip out the ns0: from the xml as per the requirement from the target system developers
i added the following config in the JMS Adapter:
number 1
XMLAnonymizerBean
Local Enterprise Bean
0
0
anonymizer.acceptNamespaces
http://www.host.com/aoc "
0
anonymizer.quote
and i get the following error:
2010-03-16 19:43:13 Error Adapter Framework caught exception: Object not found in lookup of XMLAnonymizerBean.
2010-03-16 19:43:13 Error Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of XMLAnonymizerBean..
any thoughts on what i have done wrong???Hi Michal
i got it resolved... i missed the AF_Modules off the front.....
that's what you get after a 12 hour shift clearing issues! grrrrrr!
i am on PI7.11
p.s...
apparently you are not allowed any points!
You are about to mark the message "Re: Object not found in lookup of XMLAnonymizerBean.." by Michal_Krawczyk_PIXI as correct which means you found the information in the message to be the right answer to the original question. If you believe this message was only helpful but not correct, please go back and click "Helpful" next to the message. Otherwise, click "Mark Message" to rate the message and return to the message page.
Note, marking a message as helpful or correct can not be undone. If you don't want to do this, click "Cancel" to go back to the question.
An error has occured while assigning points. Please refresh the thread view and try again.
Edited by: Barry Neaves on Mar 16, 2010 8:08 PM -
EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT
Hi All ,
I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
1 . 3 EJB3.0 session DCs
2. 1 JPA DC
I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
--- Deploying file(s):
D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
--- Status:
Deploy finished with warnings.
--- Description:
S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
Name:erecapp
Vendor:asianpaints.com
Location:J2N_ERECTT_D
Version:20090217100038
Deploy status:Warning
Version:HIGHER
Description:
1. Exception has been returned while the 'asianpaints.com/erecapp' 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.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:WarningYou have to give an explicit data source in your persistence.xml to solve this error normaly.
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="YOUR_UNIT">
<jta-data-source>DSNAME</jta-data-source>
Frank -
Object not found in lookup of SetDynamicConfiguration.
Hi,
We are doing File to Proxy Scenario, in the File adapter we used the SetDynamicConfiguration as the module with module Type as Local enterprise Bean and Paramaters as
DynamicFeedeNS and _Simulate.
during testing the File adapter shows log as "Attempt to process file failed with com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SetDynamicConfiguration".
Please suggest as how to solve this problem.
No mapping is done in our scenario and the rest are handeled at ERP.
thanks
ArchanaaHi,
first of all go to the NWA and check, if your module is active. Then check the JNDI name.
In the module chain you just enter the JNDI name, nothing else.
Also look into these links
http://help.sap.com/saphelp_nwpi71/helpdata/en/e9/61e1407e858031e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nwpi71/helpdata/en/16/2da04028f40160e10000000a1550b0/frameset.htm
SDM Troubleshooting for the error:
http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm
/people/udo.paltzer/blog/2007/04/26/new-sap-netweaver-process-integration-release-planned-for-2007
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00838345-708c-2a10-1199-9514c0b0a91c
Regards
Aashish Sinha
PS : reward points if helpful -
Object not found in lookup of RequestResponseBean.
hi all,
i am doing the scenario file to rfc to file without BPM .
I am facing the problem in my sender communication channel. that is
Error: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RequestResponseBean.
i have checked all spelling by reading sdn post . but still i am facing the same problem.
help me regarding this.
thanks & regards
Anup BanerjeeHi,
->The bean which you configured at the communication channel level under Module tab is case sensitive.
-->Please check the module name once again and maintain the proper name and try it.
this scenario works only if your SP>=SP19(3.0) & SP>=SPs10(7.0)
In Receiver Communication channel you have to specify
Processing Sequence as
1 AF_Modules/RequestResponseBean Local Enterprice Bean 1
2 CallSapAdapter Local Enterprice Bean 2
3 AF_Modules/ResponseOnewayBean Local Enterprice Bean 3
Module Configuration as
1 passThrough true
3 receiverChannel FileReceiver(Your Receiver communication channel name)
3 receiverService BusinessServive_RCVR(Receiver Business serviece)
regards,
ganesh. -
NameNotFoundException: Object not found in lookup
Hi all!
I have a problem with my Netweaver SP18 WebAS EJB application. The JNDI lookup fails with the following runtime error:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CaTreeServerIFBean.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
at com.sap.engine.services.jndi.implserver.ServerContextRedirectableImpl.lookup(ServerContextRedirectableImpl.java:80)
at com.sap.engine.services.jndi.implserver.ServerContextImplp4_Skel.dispatch(ServerContextImplp4_Skel.java:555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
predecessor system -
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CaTreeServerIFBean.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
at com.sap.engine.services.jndi.implserver.ServerContextRedirectableImpl.lookup(ServerContextRedirectableImpl.java:80)
at com.sap.engine.services.jndi.implserver.ServerContextImplp4_Skel.dispatch(ServerContextImplp4_Skel.java:555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
I use the following code to lookup the EJB:
Object homeTreeObj = ctx.lookup("sap.com/anafee-server-ear/CaTreeServerIFBean");
I think the JNDI name should be right, because it's a composite name
of "provider-name/application-name/EJB-name".
My provider-name is defined in the application-j2ee-engine.xml:
<application-j2ee-engine>
<provider-name>sap.com</provider-name>
<fail-over-enable mode="disable" />
</application-j2ee-engine>
My application-name is defined in the application.xml:
<application>
<display-name>anafee-server-ear</display-name>
<description>EAR description</description>
<module>
<ejb>anafee-server-ejb-3_2.jar</ejb>
</module>
</application>
My Session EJB is declared in the ejb-jar.xml:
<session>
<description>test</description>
<ejb-name>CaTreeServerIFBean</ejb-name>
<home>com.catenic.anafee.server.common.serverinterface.CaTreeServerIFHome</home>
<remote>com.catenic.anafee.server.common.serverinterface.CaTreeServerIF</remote>
<ejb-class>com.catenic.anafee.server.common.serverinterface.CaTreeServerIFBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-ref>
<ejb-ref-name>ejb/CaFastReaderManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.catenic.anafee.server.manager.reader.CaFastReaderManagerHome</home>
<remote>com.catenic.anafee.server.manager.reader.CaFastReaderManager</remote>
<ejb-link>CaFastReaderManagerBean</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/CaTreeManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type> <home>com.catenic.anafee.server.manager.tree.CaTreeManagerHome</home>
<remote>com.catenic.anafee.server.manager.tree.CaTreeManager</remote>
<ejb-link>CaTreeManagerBean</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/CaTNBasicManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.catenic.anafee.server.manager.tree.CaTNManagerHome</home> <remote>com.catenic.anafee.server.manager.tree.CaTNBasicManager</remote>
<ejb-link>CaTNBasicManagerBean</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/CaTreeRole2IFMappingService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.catenic.anafee.server.manager.rolemapping.tree.CaTreeRole2IFMappingServiceHome</home>
<remote>com.catenic.anafee.server.manager.rolemapping.tree.CaTreeRole2IFMappingService</remote>
<ejb-link>CaTreeRole2IFMappingServiceBean</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/CaRoleInfoManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.catenic.anafee.server.metadata.CaRoleInfoManagerHome</home>
<remote>com.catenic.anafee.server.metadata.CaRoleInfoManager</remote>
<ejb-link>CaRoleInfoManagerBean</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/CaNestedTreeManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.catenic.anafee.server.manager.tree.CaNestedTreeManagerHome</home>
<remote>com.catenic.anafee.server.manager.tree.CaNestedTreeManager</remote>
<ejb-link>CaNestedTreeManagerBean</ejb-link>
</ejb-ref>
</session>
Do you have any idea why the lookup fails? (I don't have any special JNDI mappings
defined in the ejb-j2ee-engine.xml, if this could matter.)
Regards,
MatthiasHi, Experts,
I have same exceiption as this one, my error message as:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of Route.
I register in Object: "Route" using JNDI in my RMI over IIOP server. However in my SAP Web Dynpro application, the javaBean model cannot talk with external RMI over IIOP server. my source code as:
Context ctx = new InitialContext();
Object obj = ctx.lookup("Route");
route = (Route)PortableRemoteObject.narrow(obj, Route.class);
How to make SAP J2EE server talk with external Cobra Server? -
EJB3.0 App Deplyed wid warnings : Object not found in lookup of JPA-DEFAULT
Hello Friends
I am getting this warning while deploying this EJB 3.0 Application
here I have
1) 4 DCs with session beans
2) One Entity DC
I have checked my jta-data-source its added properly
here is the deployment stack trace
Description:
1. Exception has been returned while the 'asianpaints.com/hssp_app_new' 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.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:WarningOK, you have properly declared the data source for your persistence unit in the persistence.xml. But you also have to maintain this data source (alias) on the server, i.e. it has to be created explicitly.
Check this [document|http://help.sap.com/saphelp_nwce711/helpdata/en/46/96ec3c33621e5ce10000000a1553f6/frameset.htm].
HTH!
-- Vladimir
PS: Please take your time to go through the [Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] and do not crosspost to multiple forums. -
Object not found in lookup of SapXIJDBCAdapterService..
Hi
We are getting following error when we try to send messages to third party system using JDBC Adapter:
Delivery of the message to the application using connection AFW failed, due to: Object not found in lookup of SapXIJDBCAdapterService..
We processed few messages, but it stopped all of a sudden. No changes made to the system.
Any ideas?
Thanks in advance,
Regards
ChanduHi Vijaya,
The message status is set to be "to be delivered". But, we are able to manually process the messages via the JDBC Adapter using the MessagingSystem GUI.
Is something stopping JDBC adapter to process the queues?
I am not sure redeploying the adapter will resolve this if the problem is in the XI system.
Regards
Chandu -
Object Not found in lookup of RNIF11Module Listener
Hi All,
Facing an issue with RNIF11 in XI3.0 SP19 quality system.There is no issue in dev and production.
When we run an inerface with Rosettanet in quality we are getting following error in audit log
[Delivery of message to the application using connection RNIF11 http://sap.com/xi/XI/System failed due to :com.sap.aii.af.ra.ms.api.RecoverableException:Object not found in the lookup of RNIF11Modue Listener:com.sap.engine.services.jndi.persistent.exceptions.NamenotfoundException:Object Not found in lookup of RNIF11ModuleListener.]
When i compare JNDIRegistry in Visual Admin of Production/development and Quality, i do not find the entries
RNIF11Module Listener,
RNIFModuleListener,
RNIF11DetailsEAR,
in quality but find them in Production as well as development.
How do i get them updated in JNDIRegistry?
The interface ran well previously(but not sure when it ran successfully ) and all of a sudden when we wanted to test again in quality it is failing.
Please help.
Thanks,
PadmajaHi All,
Facing an issue with RNIF11 in XI3.0 SP19 quality system.There is no issue in dev and production.
When we run an inerface with Rosettanet in quality we are getting following error in audit log
[Delivery of message to the application using connection RNIF11 http://sap.com/xi/XI/System failed due to :com.sap.aii.af.ra.ms.api.RecoverableException:Object not found in the lookup of RNIF11Modue Listener:com.sap.engine.services.jndi.persistent.exceptions.NamenotfoundException:Object Not found in lookup of RNIF11ModuleListener.]
When i compare JNDIRegistry in Visual Admin of Production/development and Quality, i do not find the entries
RNIF11Module Listener,
RNIFModuleListener,
RNIF11DetailsEAR,
in quality but find them in Production as well as development.
How do i get them updated in JNDIRegistry?
The interface ran well previously(but not sure when it ran successfully ) and all of a sudden when we wanted to test again in quality it is failing.
Please help.
Thanks,
Padmaja
Maybe you are looking for
-
Keep external display full screen on macbook pro
Anyone know how to get an external display to go full screen and not exit full screen when using the internal display? When you click away from the full screen window or switch applications full screen automatically exits. Is there a way to write a s
-
TN Wiki TechNet Guru News: October Winners Announced
All the votes are in! And below are the results for the TechNet Guru Awards, October 2014 !!!! For a full list of winners, see the full blog post, as runners up had to be removed from this post to fit the forum max length restrictions. BizTalk Tech
-
Bw is not picking up manual entries done in sap
Hi , Can any one guide me on this. for copa we are getting data from 3 datasource for one cube. z_1_copa_510_Act 0ec_pca_3 Z_1_COPA_510_PLAN What happens if somebody did the manual entry(adjustment against something)in sap.(So BW didn't pick up units
-
Storage Array???
Dear All, Yesterday I was given a Storage Array and I have no idea what it is. It is Grey with 7 HDD M2949ESP Drives (9 GB Fujitsu HDD). I have connected to my Solaris 9 box and it is showing lots of 2 GB drives. Can anyone tell me how I can identify
-
Okidata C3400n Printer Not Printing
I'm hoping there's an iMac user out there who is driving an Okidata C3400n color printer. These are fine printers and mine is less than a year old. -- I'm a brand new Mac user. My iMac 2.8 GHz/24" computer is about five days old. -- I succeeded in do