Lookup problem

Hi,
The following message appears when I deployed to a local application server:
Error finding a suitable DataSource: Error looking up cmt-datasource at jdbc/DBConnection1DS (name not found)
I think that the problem is related to a parameter to a lookup function. What is the
expected parameter of lookup?.
Thanks,

Atena,
Bad performance can be caused by many different things. Having 5 lookups in one page is no problem in itself. However, when the number of rows displayed in a lookup drop down list is large, page loading can become slow, in particular when you have a table layout, where the contents of the drop down list are included again for each row in the table. Changing the lookup displayType to "lov" should help in such a situation,
Another reason might be that the SQL statements behing the lookups are inefficient.
Steven Davelaar,
JHeadstart Team.

Similar Messages

CSS one-armed-config and SMTP reverse lookup problems?

I was wondering if there would be potential reverse lookup problems from other company's when we try to send mail to their mail Domains.
If I configure failover for our mail server, I am thinking if we are sending mail, there could be a reverse-lookup issue, because our mail server would be configured with public IP Addresses other than what the MX record points to in DNS.
If we originate mail from our inside users, it will originate from the service IP address and not the VIP address.
Is this a valid concern?

The main advantage of this configuration is that the web servers will receive the IP address of the client that made the request. This is often required by web servers' administrators for accounting purposes.
In a one-armed configuration only, the network port ( Enet0) is used on the SCA. Only this specific port can be used for this setup. Encrypted and decrypted traffic will go through the same link
http://www.cisco.com/en/US/products/hw/contnetw/ps2083/products_configuration_example09186a00801bbf4e.shtml

Looking for tips on a OC4J/JNDI lookup problem

Hello All,
I am running into a situation where a user I have setup in Oracle Enterprise Manager 10G Instance Level Security is not able to access our JNDI resources. We have tried providing all the roles(including administrators) to this user, but to no success. For some reason it works in standalone though.
Our exception is fired when deploying the application and the spring configuration tells the app to fetch the jms connection factory from JNDI.
Caused by: javax.naming.NoPermissionException: Not allowed to look up jms/ConnectionFactory, check the namespace-access tag setting in orion-application.xml for details
+     at com.evermind.server.rmi.RMIClientConnection.handleLookupResponse(RMIClientConnection.java:873)+
+     at com.evermind.server.rmi.RMIClientConnection.handleOrmiCommandResponse(RMIClientConnection.java:337)+
+     at com.evermind.server.rmi.RMIClientConnection.dispatchResponse(RMIClientConnection.java:296)+
+     at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:278)+
+     at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:152)+
+     at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:127)+
+     at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:107)+
+     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)+
+     at java.lang.Thread.run(Thread.java:595)+
+     at com.evermind.server.rmi.RMICall.warningExceptionOriginatesFromTheRemoteServer(RMICall.java:109)+
+     at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:91)+
+     at com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:425)+
+     at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:233)+
+     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:302)+
+     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:56)+
+     ... 43 more+
I wonder if there is a specific role that OC4J is looking for to allow the app to use JNDI? One thread I read earlier mentioned granting the user RMI permission. Any tips on where this could be configured?
Our namespace section of the orion application xml file is below...
     <namespace-access>
          <read-access>
               <namespace-resource root="">
                    <security-role-mapping name="<jndi-user-role>">
                         <group name="administrators" />
                    </security-role-mapping>
               </namespace-resource>
          </read-access>
          <write-access>
               <namespace-resource root="">
                    <security-role-mapping name="<jndi-user-role>">
                         <group name="administrators" />
                    </security-role-mapping>
               </namespace-resource>
          </write-access>
     </namespace-access>
Any thoughts or recommendations for isolating and troubleshooting the problem would be highly appreciated.
Many Thanks in Advance Guys!

What Mylenium said. Although, perhaps with Forge Freeform and a huge amount of work, you might be able to fake it.

RFC LOOKUP Problem

Error while lookup Plain exception:Problem when calling an adapter by using communication channel LookupChannel (Party: , Service: R/3 System Service, Object ID:xxxxxxxxxxxxxxxxxx) Check whether the communication channel exists in the Integration Directory; also check the cache notifications for the instance Integration Server (central Adapter-Engine) Channel object with Id Channel:xxxxxxxxxxxxxxxxnot available in CPA Cache. com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel LookupChannel (Party: , Service: R/3 system , Object ID: xxxxxxxx) Check whether the communication channel exists in the Integration Directory; also check the cache notifications for the instance Integration Server (central Adapter-Engine) Channel object with Id Channel:xxxxxxxxxxxxxx
) not available in CPA Cache. at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.<init>(AdapterProxyLocal.java:61) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:98) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:38) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:270) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:70) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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 am getting above Error message when i am doing DisplayQ in Message Mapping.
Regd's
Raj

Hi,
Error looks like CPACache problem.
Refresh the CPA Cache using this url: with User PIDIRUSER
This doc will help u:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34
Also go to RWB-->Cache Notifications and check the status
Hope you have imported the Adapter Metadata correctly i.e SAP BASIS SWC correctly
Hope this helps, Rgds , Moorthy

Context lookup problem in iplanet application server 6.0 sp3?

Hi all,
I am writing codes in the following enviornment, iplanet application server 6.0 sp3 with iplanet web server 4.1 sp7 in Window 2000.
When I tried to login to the system, error occured when i try to lookup context for my session bean.
The error message is as follows:
login_process.jsp: Home / Remote Error:String index out of range: -7
[10/Apr/2002 18:09:10:5] error: Exception: SERVLET-execution_failed: Error in ex
ecuting servlet JSPRunnerSticky: java.util.EmptyStackException
Exception Stack Trace:
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:86)
at java.util.Stack.pop(Stack.java:68)
at com.netscape.server.deployment.AppComponentDescriptorUtil.popCurrentAppComponent(Unknown Source)
at com.netscape.server.servlet.servletrunner.AppInfo.popWebAppDescriptor(Unknown Source)
at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source)
at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
could anyone suggest a method to solve the problem?
Thx very much!

There is a major security breach in authenticating
iPlanet Web Server 6.0 SP3 and SP4 using Sun ONE
Directory Server. Using a valid user id, any
password except null string would allow user access
the restricted resources. iPlanet Web Server 6.0 SP5
and 4.1 SP12 worked fine with similar configuration.Did you get an answer for this?
We are having the exact same problems with our iPlanet Web server 6.0 SP3.
thank you.

EJB from stored procedure lookup problem

We are running a test case with in an EJB deployed to Oracle 8.1.6, accessing it from a Java stored procedure. It works okay if the stored procedure is called a limited number of times from a single client (client is non-Java). However, for performance testing, we are trying to run it several hundred times in sequence to better simulate the eventual production environment. Consistently on the 216th call, it fails with a NamingException from the InitialContext lookup. We can restart the client again and it will fail on the same call.
Sounds like something memory related to me. Does anyone have any ideas? I'm using standard EJB client code in my stored procedure, instantiating an InitialContext, performing a lookup on the EJB, performing a home interface create, then accessing an EJB method.
Thinking it might be that my test was too fast for whatever garbage collection is being done on the server, I tried a 2 second delay between invocations--same problem occurs, however. Should I be making a call to remove my EJBs when my stored procedure ends? If so, how would I do that?
I did try making the handle to my EJB a static variable within the stored procedure and only "creating" the EJB once. That works okay with a single client, but if I run 2 clients simultaneously, 1 will work for awhile and then eventually die trying to call the EJB method--while the other client continues to run successfully.
I'm stumped. Any insight or guidance will be greatly appreciated. Thanks.

My DBA bumped up the large_pool_size and java_pool_size settings and the problem went away. I couldn't convince him to bump the settings one at a time, so am not sure which one was at the root of the problem.
As I looked at the trace logs on the server, I also noticed that we were getting intermittent "peer disconnected socket" messages during the testing. That appears to have gone away with the pool size increases, also--in case that helps out anyone else.

DB Lookup Problem

Hi All,
I am trying to use DB LOOKUP in the mapping.
I am getting the following error. Can you through some pointers?
I am using
1. Driver = oracle.jdbc.pool.OracleConnectionPoolDataSource
2. Connection = jdbc:oracle:thin:@190.190.190.190:1528:PXI
com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel DB_LOOKUP_CHANNEL (Party: , Service: DB_LOOKUP_SERVICE, Object ID: b2096509d2383857a480e38f3f4d2abe) XI AF API call failed. Module exception: 'Error ACK handling failed: java.lang.NullPointerException'. Cause Exception: (No information available). com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel DB_LOOKUP_CHANNEL (Party: , Service: DB_LOOKUP_SERVICE, Object ID: b2096509d2383857a480e38f3f4d2abe) XI AF API call failed. Module exception: 'Error ACK handling failed: java.lang.NullPointerException'. Cause Exception: (No information available). at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:131) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:68) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:149) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:77) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: 'Error ACK handling failed: java.lang.NullPointerException'. Cause Exception: (No information available). at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214) at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283) at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:123) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:68) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:149) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:77) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Thank you
Ganges Leaves

Hi Ganges~
<i>Exception during processing the payload</i>
1) Check the Payload is a valid xml
2) Check the JDBC Adapter connection Parameters -go to Adapter Monitoring and check is this is showing Active and Green..
3) Check these blog- /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
4) Check this for Connection Parameters and drivers information-
Using JDBC Adapter posting data from Oracle database to Falt file????
For more-
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/406642ea59c753e10000000a1550b0/frameset.htm
Hope this helps,
REgards,
Moorthy

JNDI lookup problem in WAS 5.1

Hello all,
I have generated an EAR using XDoclet and MyEclipse. When I deploy this EAR on WAS 5.1, I get the following exception:
javax.naming.NameNotFoundException: Context: WarHog/nodes/WarHog/servers/server1, name: ejb/TEDIObjectManagerLocal: First component in name TEDIObjectManagerLocal not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
     at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
     at com.ibm.rmi.iiop.CDRInputStream.readBoxedIDLEntity(CDRInputStream.java:2112)
     at com.ibm.rmi.iiop.CDRInputStream.readIDLValue(CDRInputStream.java:2177)
     at com.ibm.rmi.iiop.CDRInputStream.fast_read_value(CDRInputStream.java:1734)
     at com.ibm.rmi.io.IIOPInputStream.readValueType(IIOPInputStream.java:2085)
     at com.ibm.rmi.io.IIOPInputStream.readObjectField(IIOPInputStream.java:2057)
     at com.ibm.rmi.io.IIOPInputStream.inputClassFields(IIOPInputStream.java:1765)
     at com.ibm.rmi.io.IIOPInputStream.inputObjectUsingClassDesc(IIOPInputStream.java:1348)
     at com.ibm.rmi.io.IIOPInputStream.continueSimpleReadObject(IIOPInputStream.java:420)
     at com.ibm.rmi.io.IIOPInputStream.simpleReadObjectLoop(IIOPInputStream.java:404)
     at com.ibm.rmi.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:347)
     at com.ibm.rmi.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:200)
     at com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:1367)
     at com.ibm.rmi.util.ProxyUtil.copyObject(ProxyUtil.java:450)
     at com.ibm.CORBA.iiop.UtilDelegateImpl.copyObject(UtilDelegateImpl.java:789)
     at javax.rmi.CORBA.Util.copyObject(Util.java:333)
     at com.wdc.tedi.interfaces._TransformationEngine_Stub.transform(_TransformationEngine_Stub.java:268)
     at com.wdc.tedi.web.TestHarnessBean.translate(TestHarnessBean.java:42)
     at com.wdc.tedi.web.TestHarnessBean.setDataBlob(TestHarnessBean.java:80)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)First of all, I don't really understand what the error means. Is it that the JNDI lookup failed when one of my beans tried to do a lookup on 'ejb/TEDIObjectManagerLocal'? I believe there's some configuration that went wrong (EJB reference binding or something) when I deployed the EAR. The reason I don't think it's a faulty code is because the EAR runs like a charm when I deploy it on Oracle 10g and Weblogic.
I am really stuck on this problem and shall appreciate any help that I can get. I can send the code, xdoclet tags and configuration if that might assist someone.
Thanks
-ybh6336

Hello all,
I'm still stuck on this issue. Following are the entries related to my
application when I do a 'dumpNameSpace':
   28 (top)/nodes/WarHog/servers/server1/ejb/tedi/TEDIObjectManager
   28
com.wdc.tedi.interfaces._TEDIObjectManagerHome_Stub
   29 (top)/nodes/WarHog/servers/server1/ejb/tedi/DSValueLookup
   29
com.wdc.tedi.interfaces._DSValueLookupHome_Stub
   30 (top)/nodes/WarHog/servers/server1/ejb/tedi/TransformationEngine
   30
com.wdc.tedi.interfaces._TransformationEngineHome_StubObservations:
- I only see the namespace entries for my Session beans. There's one
entity bean also which does not show up.
- I don't see anything for the Local Home interfaces, it shows only the
Home interfaces.
As additional information, I'm looking up 'TEDIObjectManagerLocal'
using 'ejb/TEDIObjectManagerLocal'. I also tried using 'local:ejb/ejb/TEDIObjectManagerLocal' (as Karthyk suggested) and
'java:comp/env/ejb/TEDIObjectManagerLocal', but that does not work
either.
Also, the XDoclet tags that I use to generate the interfaces for
TEDIObjectManager bean are as follows:
/* @ejb.bean name="TEDIObjectManager"
*           display-name="TEDIObjectManager"
*           description="TEDIObjectManager"
*           jndi-name="ejb/tedi/TEDIObjectManager"
*           local-jndi-name="ejb/TEDIObjectManagerLocal"
*           type="Stateless"
*           view-type="both"
* @ejb.util generate="physical"
* @ejb.ejb-ref ejb-name="TEDIObject"
* view-type = "local"
* ref-name = "ejb/TEDIObjectLocal"
* @oc4j.bean jndi-name="ejb/tedi/TEDIObjectManager"
*/My ejb-jar.xml looks like following for that bean:
<session >
         <description><![CDATA[TEDIObjectManager]]></description>
         <display-name>TEDIObjectManager</display-name>
         <ejb-name>TEDIObjectManager</ejb-name>
         <home>com.wdc.tedi.interfaces.TEDIObjectManagerHome</home>
         <remote>com.wdc.tedi.interfaces.TEDIObjectManager</remote>
<local-home>com.wdc.tedi.interfaces.TEDIObjectManagerLocalHome</local-home>
         <local>com.wdc.tedi.interfaces.TEDIObjectManagerLocal</local>
<ejb-class>com.wdc.tedi.ejb.TEDIObjectManagerSession</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
         <ejb-local-ref >
            <ejb-ref-name>ejb/TEDIObjectLocal</ejb-ref-name>
            <ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.wdc.tedi.interfaces.TEDIObjectLocalHome</local-home>
            <local>com.wdc.tedi.interfaces.TEDIObjectLocal</local>
            <ejb-link>TEDIObject</ejb-link>
         </ejb-local-ref>
      </session>AND following for the bean that is referencing it:
<session >
         <description><![CDATA[TransformationEngine]]></description>
         <display-name>TransformationEngine</display-name>
         <ejb-name>TransformationEngine</ejb-name>
         <home>com.wdc.tedi.interfaces.TransformationEngineHome</home>
         <remote>com.wdc.tedi.interfaces.TransformationEngine</remote>
<local-home>com.wdc.tedi.interfaces.TransformationEngineLocalHome</local-home>
<local>com.wdc.tedi.interfaces.TransformationEngineLocal</local>
<ejb-class>com.wdc.tedi.ejb.TransformationEngineSession</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
         <ejb-local-ref >
            <ejb-ref-name>ejb/TEDIObjectManagerLocal</ejb-ref-name>
            <ejb-ref-type>Session</ejb-ref-type>
<local-home>com.wdc.tedi.interfaces.TEDIObjectManagerLocalHome</local-home>
<local>com.wdc.tedi.interfaces.TEDIObjectManagerLocal</local>
            <ejb-link>TEDIObjectManager</ejb-link>
         </ejb-local-ref>
      </session>The entries in ibm-ejb-jar-bnd.xmi (generated using MyEclipse) are as
follows for the two beans:
<ejbBindings
         xmi:id="Session_bnd_1"
         jndiName="ejb/tedi/TransformationEngine">
         <ejbRefBindings xmi:id="EJBRefBnd_1"
jndiName="ejb/TEDIObjectManagerLocal">
    <bindingEjbRef href="META-INF/ejb-jar.xml#EJBLocalRef_1"/>
         </ejbRefBindings>
         <enterpriseBean
            xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_TransformationEngine" />
      </ejbBindings>
<ejbBindings
         xmi:id="Session_bnd_3"
         jndiName="ejb/tedi/TEDIObjectManager">
         <ejbRefBindings xmi:id="EJBRefBnd_2"
jndiName="ejb/TEDIObjectLocal">
    <bindingEjbRef href="META-INF/ejb-jar.xml#EJBLocalRef_2"/>
         </ejbRefBindings>
         <enterpriseBean
            xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_TEDIObjectManager" />
      </ejbBindings>I know I'm swamping the post with code, but please let me know if anyone finds something unusual.
NOTE: When deploying on WAS, in the 'Map EJB references to beans' step, I'm giving the following values for 'TransformationEngine' bean:
Reference binding: ejb/TEDIObjectManagerLocal
JNDI Name: ejb/tedi/TEDIObjectManager
There's one other similar binding that works for 'TEDIObjectManager'
bean:
Reference binding: ejb/TEDIObjectLocal
JNDI Name: ejb/TEDIObject
Everything in ejb-jar and ibm-ejb-jar-bnd.xmi look similar for this working bean, there is one difference though, I do the lookup on this one using 'java:comp/env/ejb/TEDIObjectLocal', but I've already tried that for the other one.
Really appreciate your time.
Thanks
-yogesh

JDBC Lookup problem

we are facing this problem...
from SAP we send the idoc: WP_PLU03 to PI through transaction WPMA.
PI do the data format in: XML Document Format for the Mode XMB2DB_XML (http://help.sap.com/saphelp_sem40bw/helpdata/en/4d/8c103e05df2e4b95cbcc68fed61705/frameset.htm)
but before to do this format, a couple of RFC Lookups and JDBC lookups are executed.
the important here are the JDBC lookups.
when SAP sends a lot of Articles, the WP_PLU03 generates many segments, so only one LUW is not enough,then SAP automatically separates in 2 or more LUWs as needed.
the first LUW is processed correctly, so, the JDBC adapter does good all the LOOKUPS, and the XMB2DB_XML is well formed and sent to the JDBC adapter for his process.
but, the error is in the second LUW process , when the JDBC adapter begins to do the LOOKUPS, it STOPS, without error, or any alert...
any idea?

>
Christophe PFERTZEL wrote:
> Hi Guillermo,
>
> 1 LUW = 1 IDOC = 1 msg ? Do you use the same JDBC adapter for lookups AND msg sending ? Are those lookups performed using your own UDF/class or are you using PI feature ?
>
> Have you also check for error msgs in XI/PI logs and traces ?
>
> Rgds
> Chris
hi,
1 LUW = A LOT of iDoc = MANY MSG.
I've tried both, first, only one JDBC adapter for the lookup and process the message...
result = the same problem, JDBC stops with the green circle in the RWB.
second try, 2 jdbc adapters, one for the lookup and the other for the message process,
result = the lookup jdbc adapter face the same problem.
I'm using an UDF for the lookup.
> Have you also check for error msgs in XI/PI logs and traces ?
that's the problem, PI doesn't shows error.
THANKS!

Deployable proxy lookup problem

Hello SAP Community, here is my issue:
I need to access a web service in my web dynpro application, so I generated a deployable proxy from the wsdl file and deployed it to the server. I added the proxy's ClientAPI.jar to my web dynpro build path and tried to get its interface via jndi lookup, but I get a ClassCastException.
The problem here is that when I look for my proxy in Visual Administrator's JNDI Registry, the class name is different from the one in Client API, as follows:
JNDI Registry: ConsultaPadronServiceImpl
Client API: ConsultaPadronService
Debugging the code I can see that I get ConsultaPadronServiceImpl in my lookup, but when I try to do the casting to ConsultaPadronService I get the exception.
Here is my code:
try{
          InitialContext ctx = new InitialContext();
          Object obj = ctx.lookup("wsclients/proxies/sap.com/FonhapoWS/mx.gob.conavi.sap.ws.fonhapo.FonhapoProxy");
          ConsultaPadronService ser = (ConsultaPadronService)PortableRemoteObject.narrow(obj, ConsultaPadronService.class);
          port = (WsConsultaPadron)ser.getLogicalPort("WsConsultaPadronSoapHttpPort");
     }catch (Exception ex){
          IWDMessageManager msgMgr = wdComponentAPI.getMessageManager();
          msgMgr.reportException(ex.getMessage(), true);
I really hope someone can help me out with this, I have already added the sharing reference to the proxy in my Web Dynpro project like <provider>/<EAR name> and still not working.
Regards.

Same issue here. did you resolve it?

Websphere JNDI lookup problem

Hi All
Two separate webapps, have different names for Datasources, on the same host and port. Both application work fine independently.
When we deploy both applications on the same app server(websphere), whichever we executes first gets its datasource from JNDI lookup and works fine, but when we try second application it have problem in finding its data source from JNDI lookup. If we start this second application first, it will work fine, but now another will have the same problem in its JNDI lookup.
Any idea why.
Thanks
....Ranvir

Hi All
Two separate webapps, have different names for
Datasources, on the same host and port. Both
application work fine independently.
When we deploy both applications on the same app
server(websphere), whichever we executes first gets
its datasource from JNDI lookup and works fine, but
when we try second application it have problem in
finding its data source from JNDI lookup. If we start
this second application first, it will work fine, but
now another will have the same problem in its JNDI
lookup.
Any idea why.
Thanks
....RanvirHi Ranvir,
Do you mean you try to reach the same datasource with different names or do you try to reach different datasources over the same port?
If you try the first issue you shouldn't get any trouble. At least it works fine with JBOSS for example.
But if you try to do the latter in my oppinion you don't have a JNDI problem but a problem with socket binding: the two different databases must be contacted over different ports.
What do WebSphere's logs tell?
Best regards
Andy

Lookup problem for Standalone Websphere application. What to do?

Hi friends. This is my first discussion. Coming to the topic, I have created a Data Source (DB2) in WebSphere. JNDI name has been configured. I have done the Standalone application and got over. The question is how to LOOKUP JNDI name for the StandAlone application and how to ACCESS?
The program is as follows(code snippet):
class DBConnect4 {
     public static void main(String[] args) throws NamingException, SQLException {
          Properties props = new Properties();
          props.put(Context.INITIAL_CONTEXT_FACTORY,
                    "com.ibm.websphere.naming.WsnInitialContextFactory");
          /*props.put(Context.INITIAL_CONTEXT_FACTORY,
           "com.sun.jndi.cosnaming.CNCtxFactory");*/
// --------------------the problem occurs here------------------------------------
// --------------------at props.put(Context.PROVIDER_URL,"iiop://............
          props.put(Context.PROVIDER_URL, "iiop://172.23.99.88:9064");//172.23.99.88
          System.out.println("The Connection is" + props);
          try {
               InitialContext initContext = new InitialContext(props);
               Object obj = initContext.lookup("jdbc/myDataSource");
               DataSource ds = (DataSource) obj;
               Connection connection = ds.getConnection("db2admin", "Syntel123$");
               System.out.println("Connection estblished");I have configured everything, instead I am getting the following error:
The Connection is{java.naming.provider.url=iiop://172.23.99.88:9064, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory}
The Exception is:Failed to initialize the ORB
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: com.sun.corba.se.impl.orb.ORBImpl]
     at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:318)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:392)
     at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:117)
     at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:712)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:171)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at src.DBConnect4.main(DBConnect4.java:27)
Caused by: java.lang.ClassCastException: com.sun.corba.se.impl.orb.ORBImpl
     at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:86)
     at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
     at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
     at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
     at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
     at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:309)
     ... 6 more

hi, I get the same exception in a completely different context. Could you solve your problem?
Regards,
guschra
Message was edited by:
guschra

Ejb-ref and JNDI lookup problem

Hi,
I use WLS6.1sp2. I created one EntityBean and SessionBean jar files. I tried to
use session bean to refer entity bean, I failed. The details are as following:
In EntityBean's weblogic-ejb-jar.xml, I set:
<jndi-name>cabin.CabinHome</jndi-name>
In sessionbean's ejb-jar.xml
<ejb-ref>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.titan.cabin.CabinHome</home>
<remote>com.titan.cabin.Cabin</remote>
</ejb-ref>
In sessionbean's weblogic-ejb-jar.xml
<reference-descriptor>
     <ejb-reference-description>
          <ejb-ref-name>ejb/CabinHome</ejb-ref-name>
          <jndi-name>ejb/CabinHome</jndi-name>
     </ejb-reference-description>
</reference-descriptor>
At sessionbean's client, I use
javax.naming.Context jndiContext = getInitialContext();
Object obj = jndiContext.lookup("java:comp/env/ejb/CabinHome");
When I run client file, I get the following error message:
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining name
'CabinHome']; Link Remaining Name: 'ejb/CabinHome']>
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining name
'CabinHome'
     <<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining name
'CabinHome']; Link Remaining Name: 'ejb/CabinHome']
     at com.titan.travelagent.TravelAgentBean.listCabins(TravelAgentBean.java:45)
     at com.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl.listCabins(TravelAgentBean_a4c3ph_EOImpl.java:37)
     at com.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 1, 2002 11:32:40 PM PST> <Info> <Management> <dj> <travelServer> <ExecuteThread:
'14' for queue: 'default'> <system> <> <140009> <Configuration changes for domain
saved to the repository.>
Do you know what's wrong? how to fix this problem?
Thanks in advance.
DJ

Slava,
I took "cabin." out from weblogic-ejb-jar.xml, I got the same error.
DJ
"Slava Imeshev" <[email protected]> wrote:
Hi DJ,
I think you don't need "cabin." in weblogic-ejb-jar.xml :
<jndi-name>cabin.CabinHome</jndi-name>
Regards,
Slava Imeshev
"DJ" <[email protected]> wrote in message
news:[email protected]...
Hi,
I use WLS6.1sp2. I created one EntityBean and SessionBean jar files.I
tried to
use session bean to refer entity bean, I failed. The details are asfollowing:
In EntityBean's weblogic-ejb-jar.xml, I set:
<jndi-name>cabin.CabinHome</jndi-name>
In sessionbean's ejb-jar.xml
<ejb-ref>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.titan.cabin.CabinHome</home>
<remote>com.titan.cabin.Cabin</remote>
</ejb-ref>
In sessionbean's weblogic-ejb-jar.xml
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<jndi-name>ejb/CabinHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
At sessionbean's client, I use
javax.naming.Context jndiContext = getInitialContext();
Object obj = jndiContext.lookup("java:comp/env/ejb/CabinHome");
When I run client file, I get the following error message:
- with nested exception:
[javax.naming.LinkException: [Root exception is
javax.naming.NameNotFoundException:>> Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining>name>> 'CabinHome'; Link Remaining Name: 'ejb/CabinHome']>
javax.naming.LinkException: . Root exception isjavax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remainingname
'CabinHome'
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is
javax.naming.NameNotFoundException:>> Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining>name>> 'CabinHome'; Link Remaining Name: 'ejb/CabinHome']
atcom.titan.travelagent.TravelAgentBean.listCabins(TravelAgentBean.java:45)
atcom.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl.listCabins(TravelAgentBe
an_a4c3ph_EOImpl.java:37)
atcom.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 1, 2002 11:32:40 PM PST> <Info> <Management> <dj> <travelServer><ExecuteThread:
'14' for queue: 'default'> <system> <> <140009> <Configuration changesfor
domain
saved to the repository.>
Do you know what's wrong? how to fix this problem?
Thanks in advance.
DJ

JNDI Lookup Problem (General Problem)

hi all,
i am newbie on bea products, but i have some experience on java technologies, how i fount on bea documentations and forums many people has the same problem like this, can anybody help us (me)?
problem: how is it possible to write simple client for j2ee server application? i found some posts about jndi lookup, and fount about j2ee client, but is there any doc or example how to write this j2ee client ???
i worked with many application servers and i have no problem with them (JBoss, Sun App Server, IBM Websophere, Oracle AS etc.)
some people told about jndi tree on Web Logic Server Administration console , i found this tree i my session beans looks like :
Binding Name:
TimestenExampleTimestenExample_jarInsertSubscriberBean_InsertSubscriber
Class:
test.InsertSubscriberBean_o7jk9u_InsertSubscriberImpl_1000_WLStub
why is so strange name for class or binding name ????
my session bean name is : InsertSubscriber
and it's implementation : InsertSubscriberBean
how i can lookup from client ?????
can anybody show me code snippet ???
my client looks like :
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NameClassPair;
import javax.naming.NamingEnumeration;
import javax.naming.NamingException;
import org.hibernate.property.Dom4jAccessor.ElementGetter;
public class Client {
     public static void main(String[] args) {
          Context ctx = null;
          Hashtable ht = new Hashtable();
          ht.put(Context.INITIAL_CONTEXT_FACTORY,
                    "weblogic.jndi.WLInitialContextFactory");
          ht.put(Context.PROVIDER_URL, "t3://192.9.200.222:7001");
          try {
               ctx = new InitialContext(ht);
               InsertSubscriber usagefasade = (InsertSubscriber) ctx
                         .lookup("java:comp/InsertSubscriber");
          } catch (NamingException e) {
               e.printStackTrace();
          } finally {
               try {
                    ctx.close();
               } catch (Exception e) {
                    e.printStackTrace();
}can anybody show me what is there incorrect ????
oo yes and i have weblogic.jar file into my client classpath.

Hi,
Your EJB client looks fine.
You should use the JNDI name of your ejb while doing the lookup. i.e :
InsertSubscriber usagefasade = (InsertSubscriber) ctx.lookup("..use JNDI name of EJB...");
You can use the JNDI name of the EJB that you see in the JNDI tree of weblogic. [don't use Binding Name or Class name]. you can also specify the JNDI name by "jndi-name" attribute in weblogic-ejb-jar.xml.
for more info:
http://e-docs.bea.com/wls/docs81/ejb/ejb11.html
Thanks,
Qumar Hussain

DB lookup problem with Sun One App. Server 7.0,MySQL3.x - Red hat linux 7.2

Hi Group,
I have deployed my project in sun one application server 7.0 installed in red hat linux 7.2 and database is mysql. Its working in fine in normal conditions. I could not able to get connection from datasource after I kept my server 10 hours ideal. Again its working fine once I restarted the server. Please give me any solution to prevent this.
The same project is working fine under all conditions in Sun one app server 7.0 installed in windows 2000 server without any look up probem. I Got this problem only in linux OS.
mysql datasource class com.mysql.jdbc.jdbc2.optional.MysqlDataSource
please find the below code..
Context ctx = new InitialContext();
Datasource testDS = (javax.sql.DataSource)ctx.lookup( "jdbc/testDS");
Connection con = testDs.getConnection();
connection pool settings
<jdbc-connection-pool steady-pool-size="8" max-pool-size="32" max-wait-time-in-millis="0" pool-resize-quantity="2" idle-timeout-in-seconds="0" is-isolation-level-guaranteed="false" is-connection-validation-required="false" connection-validation-method="auto-commit" fail-all-connections="false" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" name="testCP">
<property value="localhost" name="serverName"/>
<property value="3306" name="portNumber"/>
<property value="root" name="user"/>
<property value="test" name="databaseName"/>
</jdbc-connection-pool>
Regards,
Hari haran

My team solved the problem and I thought that we would share.
The version of Xalan that was packaged with the JRE, that is installed by the Sun One app server, was at least 2 versions out of date. Updating the Xalan package solves the issue and the WAR file now works.
Again, this appears to be only on the Linux version as the package deploys and works perfectly on the Windows version.

Lookup problem

Similar Messages

Maybe you are looking for