JNDI replication\lookup problems

          Hi,
          We have a WL5.1 SP12 cluster that until today consisted of 2 Solaris boxes running
          8 WL instances on the 2.6 OS.
          Today we attempted to add a third Solaris box, running 2 SP12 WL instances on the
          2.8 OS. These two new instances were identical to the other 8 in all respects apart
          from one ejb jar which they did not deploy (because of Solaris 2.8\JNI\JDK1.3.1 incompatiblilities).
          We figured that these new JVM could lookup this bean via the clustered JNDI and execute
          on one of the original 8 JVMs, so we did not deploy on these new servers. This worked
          fine on test (a 3 way cluster, on one box running Solaris 2.8 and SP10).
          However when we cut the new box in this morning we got javax.naming.NameNotFoundExceptions
          from the new JVMs.
          These new JVMs apeared to start fine, and everything looked as it should on the console,
          but still the error.
          so :
          what could it be :
          OS related - a clustering spanning 2.6 and 2.8 OSs
          SP 12 related ?
          Anybody encountered anything like this before ?
          Thanks in advance.
          Justin

          Yes, the EJB classes are in the server classpath.
          I assumed that JNDI replication occured as a resulting of enabling clustering.
          "Sabha" <[email protected]> wrote:
          >Are the ejb home/remote interfaces in the server classpath of the 2 newer
          >JVMs? Is jndi replication turned off?
          >
          >-Sabha
          >
          >"Justin" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >>
          >> We have a WL5.1 SP12 cluster that until today consisted of 2 Solaris boxes
          >running
          >> 8 WL instances on the 2.6 OS.
          >>
          >> Today we attempted to add a third Solaris box, running 2 SP12 WL instances
          >on the
          >> 2.8 OS. These two new instances were identical to the other 8 in all
          >respects apart
          >> from one ejb jar which they did not deploy (because of Solaris
          >2.8\JNI\JDK1.3.1 incompatiblilities).
          >> We figured that these new JVM could lookup this bean via the clustered
          >JNDI and execute
          >> on one of the original 8 JVMs, so we did not deploy on these new servers.
          >This worked
          >> fine on test (a 3 way cluster, on one box running Solaris 2.8 and SP10).
          >>
          >> However when we cut the new box in this morning we got
          >javax.naming.NameNotFoundExceptions
          >> from the new JVMs.
          >>
          >> These new JVMs apeared to start fine, and everything looked as it should
          >on the console,
          >> but still the error.
          >>
          >> so :
          >>
          >> what could it be :
          >>
          >> OS related - a clustering spanning 2.6 and 2.8 OSs
          >> SP 12 related ?
          >>
          >> Anybody encountered anything like this before ?
          >>
          >> Thanks in advance.
          >>
          >> Justin
          >>
          >>
          >>
          >
          >

Similar Messages

Sun App Sever 8.1 / JNDI - datasource lookup problems

I get an error when calling the ctx.lookup function. I have the datasource and the resource set up in the server OK. I can ping successfully and view the table data. I am using NetBeans 4.1 / Sun 8.1
I have been up all night (11pm - 4:30am) trying to figure this out.
    <%
        java.sql.Connection conn = null;
        java.util.Hashtable env = new java.util.Hashtable();
        javax.naming.Context ctx ;
        javax.sql.DataSource cachedDataSource;
        try {
        env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
        ctx = new javax.naming.InitialContext();
        cachedDataSource = (javax.sql.DataSource)ctx.lookup("jdbc/mysql");
        if (cachedDataSource == null)
            {out.println("<h2>The datasource is not getting set properly</h2>");
            conn = cachedDataSource.getConnection();}
        else
        { out.println("<h2>the datasource is not null and seems like it gets initialized.<h2>"); }
        } catch (javax.naming.NamingException ne) {}
          catch (java.sql.SQLException se) {}
        env = null;
        ctx = null;
        conn.close();
        conn = null;
        cachedDataSource = null;
    %>

RTFM
http://docs.sun.com/app/docs/doc/819-0079
The resource lookup in the application code looks like this:
InitialContext ic = new InitialContext();
String dsName = "java:comp/env/jdbc/HelloDbDs";
DataSource ds = (javax.sql.DataSource)ic.lookup(dsName);
Connection connection = ds.getConnection();
The resource being queried is listed in the res-ref-name element of the web.xml file as follows:
<resource-ref>
<description>DataSource Reference</description>
<res-ref-name>jdbc/HelloDbDs</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
The resource-ref section in a Sun Java System specific deployment descriptor, for example sun-web.xml, maps the res-ref-name (the name being queried in the application code) to the JNDI name of the JDBC resource. The JNDI name is the same as the name of the JDBC resource as defined in the resource file when the resource is created.
<resource-ref>
<res-ref-name>jdbc/HelloDbDs</res-ref-name>
<jndi-name>jdbc/HelloDbDataSource</jndi-name>

JMS - JNDI lookup Problem

Hi,
I am using OC4J 10g (10.1.3.1.0).
I have a standalone JMS application which tries to get QueueConnectionFactory. The application and the OC4J reside in the same machine.
This is what my code looks like
Properties parm = new Properties();
parm.setProperty("java.naming.factory.initial",
"com.evermind.server.rmi.RMIInitialContextFactory");
parm.setProperty("java.naming.provider.url",
"opmn:ormi://localhost");
parm.setProperty("java.naming.security.principal", "oc4jadmin");
parm.setProperty("java.naming.security.credentials", "oc4jadmin");
jndiContext = new InitialContext(parm);
queueConnectionFactory = (QueueConnectionFactory)jndiContext.lookup("jms/MainQueueConnectionFactory");
And my JMS.xml entry
<jms-server port="9127">
<queue-connection-factory name="MainQueueConnectionFactory" host="localhost" port="9127" password="oc4jadmin" username="oc4jadmin" location="jms/MainQueueConnectionFactory"/>
<queue name="MainQueue" location="jms/MainQueue"/>
</jms-server>
When i run my standalone, i get this exception
WARNING: Error in obtaining server list from OPMN on host localhost:6003. Please verify that OPMN is running.
JNDI API lookup failed: javax.naming.NameNotFoundException: jms/MainQueueConnectionFactory not found
Any help with this would be appreciated.
Cheers,
Sumanth

Just a guess off the top of my head but if you are using this provider URL
opmn:ormi://localhostThen you need to augment it with the OC4J instance name.
opmn:ormi://localhost:homeYou may also need to check OPMN and see what request port it is using -- do an
$ORACLE_HOME/opmn/bin/opmnctl status -portAnd then use that port in your URL as follows
opmn:ormi://localhost:<port>:homeIf it comes back as 6003 then that is the default port and thus does not need to be provided.
-steve-

Cluster-wide JNDI replication

I have a question about cluster wide JNDI replication. I am on weblogic
          7.0 sp2, solaris 8. I have 2 weblogic servers in a cluster and two
          asynchronous JVM's connect to this cluster. The two weblogic servers
          would be w1 and w2 and the JVMs would be j1
          w1 creates a stateful ejb. The handle to this ejb is put on the JNDI
          tree. A JMS message is created which contains the key to the handle
          object. A JMS message is sent which is picked up by one of the JVM's say
          j1. j1 tries to do a lookup of the handle using the key in the JMS
          message and it is not able to find the handle object.
          The reason is that j1 is trying to connect to the w2 to find the handle.
          The change to the jndi tree is not propagated to w2 yet and hence the
          error. Any ideas on why it would take so long to communicate the jndi
          tree? My jndi tree has hardly anything in it. There are a couple of JMS
          connection factories and 3 ejbs and couple of JMS queues.
          Would appreciate any kind of help. I am going to migrate storing the ejb
          handles to another persistent store instead of the jndi tree but till
          then any insight into this problem would be helpful.
          Please don't advice solutions like using Thread.sleep and trying again
          Thanks,
          Shiva.


Shiva,
          > I have a question about cluster wide JNDI replication. I am on weblogic
          > 7.0 sp2, solaris 8. I have 2 weblogic servers in a cluster and two
          > asynchronous JVM's connect to this cluster. The two weblogic servers
          > would be w1 and w2 and the JVMs would be j1
          >
          > w1 creates a stateful ejb. The handle to this ejb is put on the JNDI
          > tree. A JMS message is created which contains the key to the handle
          > object. A JMS message is sent which is picked up by one of the JVM's say
          > j1. j1 tries to do a lookup of the handle using the key in the JMS
          > message and it is not able to find the handle object.
          >
          > The reason is that j1 is trying to connect to the w2 to find the handle.
          > The change to the jndi tree is not propagated to w2 yet and hence the
          > error. Any ideas on why it would take so long to communicate the jndi
          > tree? My jndi tree has hardly anything in it. There are a couple of JMS
          > connection factories and 3 ejbs and couple of JMS queues.
          That's an interesting problem. The handle should have enough information
          to locate the EJB. Are you explicitly trying to connect to W2 from J1 or
          something? That part didn't make sense to me.
          (While it's a different approach, if you need to share data real-time in a
          cluster, use our Coherence Java clustered cache software.)
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Shiva P" <[email protected]> wrote in message
          news:[email protected]...
          >

JNDI replication within a cluster

Hi to all of you,
we successfully enabled HTTP Session replication and tested the failover. We would also like to setup a JNDI replication, so that we can use it as a storage for some shared data -- as stated in http://download.oracle.com/docs/cd/B10464_05/web.904/b10324/cluster.htm this should be enabled automatically, once EJB replication is enabled.
With some problems we finally enabled EJB replication (we configured it through orion-application.xml) and the required replication policy is propagated to our statful beans. Anyway, the JNDI is still not replicated over the machines.
We are running latest OAS 10g, cluster is MultiCast on RedHat Enterprise, replication policy for Stateful beans is set to 'onRequestEnd' (we tried all the options :), our application is normal ear with 1 ejb and 1 war archive and apart from JNDI replication, it works as expected.
Is there some trick that is not mentioned or that we may overlooked in documentation to enable JNDI replication?
Kind Regards,
Martin

Hopefully solved -- though the documentation explicitly mentions rebinding as not working, after any changes made to value stored in JNDI context you should just re-bind the value to the JNDI context; the value is replicated to other JNDI contexts.
m.

JNDI replication in cluster

Is there a way to force the JNDI replication?


It is on by default, unless you specifically disabled it:
          http://e-docs.bea.com/wls/docs61/javadocs/weblogic/jndi/WLContext.html
          REPLICATE_BINDINGS
          public static final java.lang.String REPLICATE_BINDINGS
          Cluster-specific: Specifies whether tree modifications are replicated
          and is only applicable when connecting to WebLogic Servers that are running
          in a cluster. By default, any modification to the naming tree is replicated
          across the cluster, which ensures that any server can act as a naming server
          for the entire cluster. Setting this property to false changes this behavior
          and should be done with extreme caution: a false setting means that modifications
          to the tree caused by bind, unbind, createSubcontext, and destroySubcontext
          will not be replicated.
          Understand the implications of this property before changing its default (true).
          Pothiraj <[email protected]> wrote:
          > Is there a way to force the JNDI replication?
          Dimitri

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

How to use JNDI to lookup remote EJB Home?

Hello,
I am writing a servlet to call a remote EJB on another machine.
I use JNDI to lookup remote EJBHome (not) but fail.
Any advice?
Any trick to configure application-client.xml?
Thanks!

Use com.evermind.server.rmi.RMIInitialContextFactory instead
Here an example
// EmployeeClient.java
package mypackage5;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
import java.io.*;
import java.util.*;
import java.rmi.RemoteException;
import com.evermind.server.ApplicationClientInitialContextFactory;
import com.evermind.server.rmi.RMIInitialContextFactory;
* A simple client for accessing an EJB.
public class EmployeeClient
public static void main(String[] args)
System.out.println("EmployeeClient.main(): client started...");
try
* initialize JNDI context by setting factory, url and credential
* in a hashtable
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
//env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
env.put(Context.PROVIDER_URL, "ormi://koushikm:23791/application4");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
* or set these properties in jndi.properties
* or use container defaults if that's where client got launched from
Context context = new InitialContext(env);
* Lookup the EmployeeHome object. The reference is retrieved from the
* application-local context (java:comp/env). The variable is
* specified in the assembly descriptor (META-INF/application-client.xml).
Object homeObject =
context.lookup("HelloEJB");
System.out.println("EmployeeClient.main(): bean found...");
// Narrow the reference to EmployeeHome.
HelloEJBHome home =
(HelloEJBHome) PortableRemoteObject.narrow(homeObject,
HelloEJBHome.class);
System.out.println("EmployeeClient.main(): home narrowed...");
// Create remote object and narrow the reference to Employee.
HelloEJB remote =
(HelloEJB) PortableRemoteObject.narrow(home.create(), HelloEJB.class);
System.out.println("EmployeeClient.main(): remote created...");
String message=remote.helloWorld("SUCCESS");
System.out.println(message);
} catch(NumberFormatException e) {
System.err.println("NumberFormatException: " + e.getMessage());
} catch(RemoteException e) {
System.err.println("RemoteException: " + e.getMessage());
} catch(IOException e) {
System.err.println("IOException: " + e.getMessage());
} catch(NamingException e) {
System.err.println("NamingException: " + e.getMessage());
} catch(CreateException e) {
System.err.println("CreateException: " + e.getMessage());
Hello,
I am writing a servlet to call a remote EJB on another machine.
I use JNDI to lookup remote EJBHome (not) but fail.
Any advice?
Any trick to configure application-client.xml?
Thanks!

URGENT - Lookup Problem Again

It is working if I try to use JNDI to lookup the EJB.
Can the client program use env-ref (just like it is another
EJB program) and deferred the mapping to the real jndi-name in an external XML file?
Or JNDI is the only way ??

ejb-refs from a Java client aren't supported, only from a J2EE component.
Seth
Friend wrote:
It is working if I try to use JNDI to lookup the EJB.
Can the client program use env-ref (just like it is another
EJB program) and deferred the mapping to the real jndi-name in an external XML file?
Or JNDI is the only way ??

JNDI replication problems in WebLogic cluster.

I need to implement a replicable property in the cluster: each server could
update it and new value should be available for all cluster. I tried to bind
this property to JNDI and got several problems:
1) On each rebinding I got error messages:
<Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
to bind an object under the name example.TestName in the jndi tree. The
object you have bound java.util.Date from 10.1.8.114 is non clusterable and
you have tried to bind more than once from two or more servers. Such objects
can only deployed from one server.>
<Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
example.TestName for the object java.util.Date from 10.1.9.250 under the
bind name example.TestName in the jndi tree.>
As I understand this is a designed behavior for non-RMI objects. Am I
correct?
2) Replication is still done, but I got randomly results: I bind object to
server 1, get it from server 2 and they are not always the same even with
delay between operation in several seconds (tested with 0-10 sec.) and while
it lookup returns old version after 10 sec, second attempt without delay
could return correct result.
Any ideas how to ensure correct replication? I need lookup to return the
object I bound on different sever.
3) Even when lookup returns correct result, Admin Console in
Server->Monitoring-> JNDI Tree shows an error for bound object:
Exception
javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
Unresolved:'example' ; remaining name ''
My configuration: admin server + 3 managed servers in a cluster.
JNDI bind and lookup is done from stateless session bean. Session is
clusterable and deployed to all servers in cluster. Client invokes session
methods throw t3 protocol directly on servers.
Thank you for any help.

It is not a good idea to use JNDI to replicate application data. Did you consider
using JMS for this? Or JavaGroups (http://sourceforge.net/projects/javagroups/) -
there is an example of distibuted hashtable in examples.
Alex Rogozinsky <[email protected]> wrote:
I need to implement a replicable property in the cluster: each server could
update it and new value should be available for all cluster. I tried to bind
this property to JNDI and got several problems:
1) On each rebinding I got error messages:
<Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
to bind an object under the name example.TestName in the jndi tree. The
object you have bound java.util.Date from 10.1.8.114 is non clusterable and
you have tried to bind more than once from two or more servers. Such objects
can only deployed from one server.>
<Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
example.TestName for the object java.util.Date from 10.1.9.250 under the
bind name example.TestName in the jndi tree.>
As I understand this is a designed behavior for non-RMI objects. Am I
correct?
2) Replication is still done, but I got randomly results: I bind object to
server 1, get it from server 2 and they are not always the same even with
delay between operation in several seconds (tested with 0-10 sec.) and while
it lookup returns old version after 10 sec, second attempt without delay
could return correct result.
Any ideas how to ensure correct replication? I need lookup to return the
object I bound on different sever.
3) Even when lookup returns correct result, Admin Console in
Server->Monitoring-> JNDI Tree shows an error for bound object:
Exception
javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
Unresolved:'example' ; remaining name ''
My configuration: admin server + 3 managed servers in a cluster.
JNDI bind and lookup is done from stateless session bean. Session is
clusterable and deployed to all servers in cluster. Client invokes session
methods throw t3 protocol directly on servers.
Thank you for any help.--
Dimitri

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.

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

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

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

JNDI replication\lookup problems

Similar Messages

Maybe you are looking for