HttpClusterServlet and cluster JNDI tree

          Hello,
          Our ear is being deployed in a clustered environment. The ear contains a jar
          (multiple ejbs), a web app war, and a webservice war. The httpClusterServlet
          proxy is being run in a server outside the cluster, on port 80. When our servlets
          try to do a JNDI lookup for any of the ejbs, a Naming Exception is thrown. The
          URL for the InitialContext provider is using port 80. So I assume that the lookup
          request is going to the proxy server, which isn't aware of the cluster JNDI tree.
          Aside from moving the proxy inside the cluster (the server configuration is being
          controlled by another developer), is there anyway to resolve this? Changing the
          URL of the provider for the lookups would require knowing the ports of the cluster
          servers.
          Thanks,
          Bob

Similar Messages

Common JNDI Tree

We want to run 2 instances of WLS on one machine and 2 on other machine.
Is there any way to setup a common jndi tree. so components on all 4 instances can access the same jndi URL.
any help will be greatly appreciated.
Thanks

Hi ,
You would have to set them up on a cluster and the JNDI tree by default is replicable .
But it seems like there is a bug in the JNDI Implementation and if any objects
unbind or rebind , they dont get reflected on the replicated JNDI tree.
Cheers,
Naggi
Baraut wrote:
We want to run 2 instances of WLS on one machine and 2 on other machine.
Is there any way to setup a common jndi tree. so components on all 4 instances can access the same jndi URL.
any help will be greatly appreciated.
Thanks

JNDI Tree Going away!

I've been experimenting with JMS clustering and foreign providers under WebLogic
8.1. But I keep running into this problem: The JNDI tree goes away! When I right
click the server and select JNDI tree, the new screen only shows the name of
my
server at the top. Rebooting the server does not fix the problem. Has anybody
else run into this??
Thanks
Dave

This bug was acknowledged by BEA support, but I was able to fix it by putting the
proper Sonic classes in my startWebLogic.sh script.
FYI
Dave
"David Mrozek" <[email protected]> wrote:
>
I've been experimenting with JMS clustering and foreign providers under
WebLogic
8.1. But I keep running into this problem: The JNDI tree goes away!
When I right
click the server and select JNDI tree, the new screen only shows the
name of
my
server at the top. Rebooting the server does not fix the problem. Has
anybody
else run into this??
Thanks
Dave

Jndi tree different in different servers in a cluster?

I bind a Properties object in jndi tree and it comes up fine in one node
i.e. I can see it in the jndi tree on one Server.
But I cannot see it in another Server in the cluster. Any idea why this
behaviour?
the code looks like this:
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, JNDITags.JNDI_FACTORY);
h.put(WLContext.CREATE_INTERMEDIATE_CONTEXTS, new
Boolean(true));
if (user != null) {
h.put(Context.SECURITY_PRINCIPAL, user);
if (pwd == null)
pwd = "";
h.put(Context.SECURITY_CREDENTIALS, pwd);
InitialContext ic = new InitialContext(h);
Context ctx = ic.createSubcontext( "yy");
ctx.bind( "lp", props );
ctx.close();
ic.close();
Komal

If you are trying to do the lookup "at startup time for server 2", the JNDI
replication may not be complete yet. We had a similar problem trying to deploy
MDBs against JMS destinations on remote servers...
komal mangtani wrote:
Can't a bind an object on 1 server and do a lookup on other server ?
Like in my case, when 1st server starts, it binds the object to the jndi
tree in its startup class.
Then the second server comes up and does a lookup on the same object in its
own startup class.
Isn't the jndi tree, suppose to get replicated to another server?
Komal.
komal mangtani wrote:
I bind a Properties object in jndi tree and it comes up fine in one node
i.e. I can see it in the jndi tree on one Server.
But I cannot see it in another Server in the cluster. Any idea why this
behaviour?
the code looks like this:
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, JNDITags.JNDI_FACTORY);
h.put(WLContext.CREATE_INTERMEDIATE_CONTEXTS, new
Boolean(true));
if (user != null) {
h.put(Context.SECURITY_PRINCIPAL, user);
if (pwd == null)
pwd = "";
h.put(Context.SECURITY_CREDENTIALS, pwd);
InitialContext ic = new InitialContext(h);
Context ctx = ic.createSubcontext( "yy");
ctx.bind( "lp", props );
ctx.close();
ic.close();
Komal

Loading the JNDI Tree in a Cluster

Is there any special processing that occurs with a Startup class when it
          has been
          started via the cluster level properties file?
          We've got a class that loads the JNDI tree for various configuration for
          our application.
          It's written that so that it will rebind() entries in the tree, so two
          copies could work together
          in the cluster, but I'd like to prevent the double work. (One copy
          bind()s an element, then the other rebind()s the same value.
          Are Startups "cluster" aware, and is there any magic to simplify this
          for me (or do I do the
          work of creating a semaphore-like setup in my class to detect two copies
          running.)
          Thanks in Advance,
          Brian Homrich
          Chicago, Illinois


In the startup class on Environment object if you don't set
          replicatebindings to false, in a cluster all locally bound objects will be
          replicated. The default it true. So, jndi will try replicate every
          bind/rebind etc.
          Rebind will remove old copy and bind the new copy. But I have to understand
          more what you are trying to do, before I can be of any help.
          - Prasad
          Brian Homrich wrote:
          > Is there any special processing that occurs with a Startup class when it
          > has been
          > started via the cluster level properties file?
          >
          > We've got a class that loads the JNDI tree for various configuration for
          > our application.
          > It's written that so that it will rebind() entries in the tree, so two
          > copies could work together
          > in the cluster, but I'd like to prevent the double work. (One copy
          > bind()s an element, then the other rebind()s the same value.
          >
          > Are Startups "cluster" aware, and is there any magic to simplify this
          > for me (or do I do the
          > work of creating a semaphore-like setup in my class to detect two copies
          > running.)
          >
          > Thanks in Advance,
          >
          > Brian Homrich
          > Chicago, Illinois

Are Connection Factory and JMS Queue supposed to be in JNDI tree

I have created Connection Factory and JMS Queue. I am expecting to find both in JNDI tree. Where, in the http://localhost:7001/console/consolejndi.portal, could I find them? I mean, in which branch of the JNDI tree?

Hi,
You should find them following exactly the way you define their JNDI Names... Make sure you are looking into the JNDI tree for the right managed server... Pay attention into the targets of your connection factory and queue...
For example, a JNDI name jms.myConnectionFactory (or jms/myConnectionFactory) targeted to soa_server1 will appear under soa_server1 / jms / myConnectionFactory ...
Hope this helps...
Cheers,
Vlad

JNDI tree access for code outside servlets and EJBs and JSPs

Can code outside EJBs, Servlets and JSPs have access to the JNDI tree?
For example, in a web application, web.xml has a env-entry declaration which I want to access from a POJO which is called by a JSP in the web app. Is this permissible?

Can code outside EJBs, Servlets and JSPs have access
to the JNDI tree?
For example, in a web application, web.xml has a
env-entry declaration which I want to access from a
POJO which is called by a JSP in the web app. Is
this permissible?Yes. Read the JNDI tutorial.

Shared JNDI Tree WL 10 and SAP Web AS

Hi,
in my current project, the vision is to have a joined JNDI tree for the platform. Currently we have a WL 10 server hosting a web application with its own JNDI tree and a SAP Web Application Server also with an JNDI tree. The server are not clustered. The vision is to merge the JNDI trees and have one central instance which can be accessed by both AS. Is this a feasable solution? What is required to setup the central/share JNDI tree and which server should host the JNDI tree? Can anyone point me to some relevant documentation?

Cord Plasse <> writes:
You can't really share the tree, although you could federate from one
namespace to the other.
andy
Hi,
in my current project, the vision is to have a joined JNDI tree for the platform. Currently we have a WL 10 server hosting a web application with its own JNDI tree and a SAP Web Application Server also with an JNDI tree. The server are not clustered. The vision is to merge the JNDI trees and have one central instance which can be accessed by both AS. Is this a feasable solution? What is required to setup the central/share JNDI tree and which server should host the JNDI tree? Can anyone point me to some relevant documentation?

Trouble in storing and retrieving RMI object in Weblogic 7 JNDI tree.

I have created a simple server (BankImpl), implementing a RMI interface
called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
class using
"rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
in Weblogic
server 7 under the name of "PeopleBank".
After the binding, I can see the stub class in the JNDI tree, but with a
different name: BankImpl_WLStub.class). when a
client program is trying to lookup the stub associated with "PeopleBank", it
failed with a puzzling message:
java.io.NotSerializableException: BankImpl_WLStub
Why a stub of a RMI object is not serializable? Does Weblogic needs a
different rmic to generate RMI stubs?
Thanks,
Lian

I have created a simple server (BankImpl), implementing a RMI interface
called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
class using
"rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
in Weblogic
server 7 under the name of "PeopleBank".
After the binding, I can see the stub class in the JNDI tree, but with a
different name: BankImpl_WLStub.class). when a
client program is trying to lookup the stub associated with "PeopleBank", it
failed with a puzzling message:
java.io.NotSerializableException: BankImpl_WLStub
Why a stub of a RMI object is not serializable? Does Weblogic needs a
different rmic to generate RMI stubs?
Thanks,
Lian

Jndi tree

I am running WLS (non clustering) on two machines (Mach A and Mach B),
each host 1 bean (Bean A and Bean B). Bean A and B need to get
reference to one another. Are there 2 JNDI tree (one at each WLS) or is
there a way I can setup 1 JNDI tree so that both Beans can be looked up
at one JNDI url?

If these machines were clustered would you need to make this setting in the
properties file or would the cluster take care of it?
Cameron Purdy <[email protected]> wrote in message
news:8ghgnb$rol$[email protected]..
You can set up one to use the other. In your <jre>/lib/jndi.properties
file:
java.naming.factory.initial=jndi.WLInitialContextFactory
java.naming.provider.url=t3://<ipaddress>:<port>
Cameron Purdy, LiveWater
"David Tran" <[email protected]> wrote in message
news:[email protected]..
I am running WLS (non clustering) on two machines (Mach A and Mach B),
each host 1 bean (Bean A and Bean B). Bean A and B need to get
reference to one another. Are there 2 JNDI tree (one at each WLS) or is
there a way I can setup 1 JNDI tree so that both Beans can be looked up
at one JNDI url?

JNDI tree replicated to an external global naming service

Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Yes, you can use federation do achieve this but remember federation is
just putting a refence that points to the original JNDI provider and
doesn't really give you replication of the entire JNDI namespace.
Guillaume Bedard wrote:
Hi!
Can you elaborate as to what makes it impossible?
What if we "federate" the two clusters, which have their
own autonomous naming systems, by binding a reference to
these naming systems in another naming service?
Thanks,
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
No
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3cab4a00$[email protected]..
More specifically, I would like be able to join two clusters
(each having their own cluster-wide replicated naming tree)
by replicating their bindings into a global naming tree,
possibly hosted by a dedicated "jndi" server.
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
My immediate response would be 'No', but I am confused as to what
are
you
trying to achieve?
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3ca9cd9c$[email protected]..
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Why in jndi tree I find the remote interface to String is so strange?

          when I view the jndi tree in weblogic server 61sp1
          I found such information:
          Bind Name: Enterprise1
          Class: class $Proxy94
          to String: ClusterableRemoteRef(10.132.0.161 [10.132.0.161])/275
          hash Code: 4568198
          Why the Class and to String like such? my license.bea
          is not a cluster version.


          Thanks you very much
          "Kumar Allamraju" <[email protected]> wrote:
          >EJB's are compiled with clustering options "ON". that's why you are seeing
          >a
          >ClusterableRemoteRef.
          >Don't worry, you will not be able to run WLS instances in cluster mode
          >without having a cluster license.
          >
          >--
          >--
          >Kumar
          >
          >"Eric nie" <[email protected]> wrote in message
          >news:3ca8238a$[email protected]..
          >>
          >> when I view the jndi tree in weblogic server 61sp1
          >> I found such information:
          >>
          >> Bind Name: Enterprise1
          >> Class: class $Proxy94
          >> to String: ClusterableRemoteRef(10.132.0.161 [10.132.0.161])/275
          >> hash Code: 4568198
          >>
          >> Why the Class and to String like such? my license.bea
          >> is not a cluster version.
          >>
          >
          >

Replicated jndi tree

We are running multiple WL servers (vers. 2.5.1 non-clustered)
registered to
different ports and would like to have the component names of one server
known to the other. Is there a way of doing this w/o having to
hard-code
that component A lives on machineX : port 999 or buying the clustering
option?

Yes, you can use federation do achieve this but remember federation is
just putting a refence that points to the original JNDI provider and
doesn't really give you replication of the entire JNDI namespace.
Guillaume Bedard wrote:
Hi!
Can you elaborate as to what makes it impossible?
What if we "federate" the two clusters, which have their
own autonomous naming systems, by binding a reference to
these naming systems in another naming service?
Thanks,
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
No
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3cab4a00$[email protected]..
More specifically, I would like be able to join two clusters
(each having their own cluster-wide replicated naming tree)
by replicating their bindings into a global naming tree,
possibly hosted by a dedicated "jndi" server.
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
My immediate response would be 'No', but I am confused as to what
are
you
trying to achieve?
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3ca9cd9c$[email protected]..
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Managed Server unreached after view JNDI tree

I have issue with WLS managed server to see if anyone know that
Version WLS 10.3.1.0
I create 11G soa domain , soa_server1 as managed server .
When I open JNDI tree window of soa_server1 , I can see some error mark in eis node , when I close it . I am never able to see the view JNDI tree link ,and state of soa_server1 change to UNKNOW. actually soa_server1 still working
Again , try to use WSLT to browse JNDI of soa_server1
got this exception:
Caused by: java.rmi.UnmarshalException: Problem finding error class; nested exception is:
java.lang.ClassNotFoundException: oracle.sdpinternal.messaging.driver.email.EmailResourceAdapter
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:217)
... 35 more
Caused by: java.lang.ClassNotFoundException: oracle.sdpinternal.messaging.driver.email.EmailResourceAdapter
at weblogic.utils.classloaders.GenericClassLoader.checkMagicNumber(GenericClassLoader.java:432)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:336)
at weblogic.rmi.utils.WLRMIClassLoaderDelegate.loadClass(WLRMIClassLoaderDelegate.java:215)
at weblogic.rmi.utils.WLRMIClassLoaderDelegate.loadClass(WLRMIClassLoaderDelegate.java:135)
at weblogic.rmi.utils.Utilities.loadClass(Utilities.java:306)
Any clue?
Kevin
Edited by: kyi on Oct 23, 2009 12:14 PM

Hi Kyi,
Can you check if that class had been loaded successfully?.
For JRocket :- add "-Xverbose:class,load -Xverboselog:classload.txt" to JVM options.
For Sun :- add "-verbose:class" to JVM options.
Thanks.
Vijay Bheemineni.

Cluster jndi error

          Hi:
          we have deploye samples cluster ejb teller and account to a cluster environment..one
          admin server and one manager server in the same machine(use multi-ip)..another
          manager server on another machine..two manager server join a cluster,we use weblogic6.0sp2,when
          we want see manager server's jndi tree .got the error messages..and I read from
          bea's online document..in a cluster environment ..any join cluster's manager server
          have the same jndi tree..but if admin server not in the cluster ,it's jndi tree
          will the same with the other manager servers?and how to deploye ejb to the cluster
          correclly?should i set call-by-reference to false in weblogic-ejb.xml?thanks your
          comment...
          javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException:
          failed to unmarshal interfa
          ce javax.naming.NamingEnumeration; nested exception is:
          java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          This error could
          indicate that a component was deployed on a cluster member but not other members
          of that cluster. Make sure th
          at any component deployed on a server that is part of a cluster is also deployed
          on all other members of that cl
          uster
          java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          This error could indicat
          e that a component was deployed on a cluster member but not other members of that
          cluster. Make sure that any c
          omponent deployed on a server that is part of a cluster is also deployed on all
          other members of that cluster
          at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:143)
          at weblogic.rjvm.MsgAbbrevInputStream.resolveClassOverride(MsgAbbrevInputStream.java:84)
          at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectI
          nputStream.java:276)
          at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1142)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:374)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:106)
          at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:122)
          at weblogic.jndi.internal.BindingEnumeration.readExternal(BindingEnumeration.java:55)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:103)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:114)
          at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:47)
          at weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:136)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:251)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
          at weblogic.jndi.internal.ServerNamingNode_WLStub.listBindings(ServerNamingNode_WLStub.java:374)
          at weblogic.jndi.internal.WLContextImpl.listBindings(WLContextImpl.java:293)
          at javax.naming.InitialContext.listBindings(InitialContext.java:399)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:74)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)


          Just the same happens to me. I think the problem is that the management server
          can not download the ejb stub from the other server. If you deploy the ejb also
          in the management server you solve the problem, but that's not the way it should
          work... I think this is a bug of weblogic.
          I've also found another nice one like that. I have 2 machines in cluster, and
          a third one out of the cluster, all of them running weblogic. A class running
          in this last weblogic makes a call to a bean that is deployed in the cluster (wants
          to act just as a client, like if you were testing your ejb from your machine against
          the servers). Then the same problem occurs, the client can not download the class
          as any RMI client does, showing you the same error. Actually any client not running
          within weblogic can do that, but when the weblogic classloader is in the middle
          that does not work.
          "weber" <[email protected]> wrote:
          >
          >Hi:
          > we have deploye samples cluster ejb teller and account to a cluster
          >environment..one
          >admin server and one manager server in the same machine(use multi-ip)..another
          >manager server on another machine..two manager server join a cluster,we
          >use weblogic6.0sp2,when
          >we want see manager server's jndi tree .got the error messages..and I
          >read from
          >bea's online document..in a cluster environment ..any join cluster's
          >manager server
          >have the same jndi tree..but if admin server not in the cluster ,it's
          >jndi tree
          >will the same with the other manager servers?and how to deploye ejb to
          >the cluster
          >correclly?should i set call-by-reference to false in weblogic-ejb.xml?thanks
          >your
          >comment...
          >
          >
          >
          >
          >
          >
          >javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException:
          >failed to unmarshal interfa
          >ce javax.naming.NamingEnumeration; nested exception is:
          >java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          >This error could
          >indicate that a component was deployed on a cluster member but not other
          >members
          >of that cluster. Make sure th
          >at any component deployed on a server that is part of a cluster is also
          >deployed
          >on all other members of that cl
          >uster
          >java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          >This error could indicat
          >e that a component was deployed on a cluster member but not other members
          >of that
          >cluster. Make sure that any c
          >omponent deployed on a server that is part of a cluster is also deployed
          >on all
          >other members of that cluster
          >at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:143)
          >at weblogic.rjvm.MsgAbbrevInputStream.resolveClassOverride(MsgAbbrevInputStream.java:84)
          >at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectI
          >nputStream.java:276)
          >at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          >at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          >at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262)
          >at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
          >at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          >at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1142)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:374)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:106)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:122)
          >at weblogic.jndi.internal.BindingEnumeration.readExternal(BindingEnumeration.java:55)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:103)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:114)
          >at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:47)
          >at weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:136)
          >at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:251)
          >at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
          >at weblogic.jndi.internal.ServerNamingNode_WLStub.listBindings(ServerNamingNode_WLStub.java:374)
          >at weblogic.jndi.internal.WLContextImpl.listBindings(WLContextImpl.java:293)
          >at javax.naming.InitialContext.listBindings(InitialContext.java:399)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:74)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          >

HttpClusterServlet and cluster JNDI tree

Similar Messages

Maybe you are looking for