StackOverflowError while displaying JNDI tree -WLS 92
Hi,
I have a domain with two clusters. I need to display jndi tree of one server, but when i try to do, the following error appear in the log.
####<Apr 28, 2008 1:43:45 PM CDT> <Warning> <netuix> <inweb2.> <posAdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1209408225440> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3Dpos2%2CType%3DServer%22%29.>
####<Apr 28, 2008 1:44:05 PM CDT> <Error> <netuix> <inweb2.> <posAdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1209408245929> <BEA-423167> <An exception or error occurred in the backing file [com.bea.jsptools.tree.JNDINavTreeBacking] while executing its preRender method. It was java.lang.StackOverflowError
java.lang.StackOverflowError
at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2218)
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2382)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2443)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515)
at java.io.DataInputStream.readInt(DataInputStream.java:353)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2720)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:930)
at java.util.ArrayList.readObject(ArrayList.java:586)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.rjvm.MsgAbbrevInputStream.readArrayList(MsgAbbrevInputStream.java:591)
at weblogic.rjvm.MsgAbbrevInputStream$NestedObjectInputStream.readArrayList(MsgAbbrevInputStream.java:690)
at weblogic.rmi.cluster.BasicReplicaList.readExternal(BasicReplicaList.java:310)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.rjvm.MsgAbbrevInputStream.readObjectWL(MsgAbbrevInputStream.java:554)
at weblogic.rjvm.MsgAbbrevInputStream$NestedObjectInputStream.readObjectWL(MsgAbbrevInputStream.java:676)
at weblogic.rmi.cluster.BasicReplicaHandler.readExternal(BasicReplicaHandler.java:751)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.rjvm.MsgAbbrevInputStream.readObjectWL(MsgAbbrevInputStream.java:554)
at weblogic.rjvm.MsgAbbrevInputStream$NestedObjectInputStream.readObjectWL(MsgAbbrevInputStream.java:676)
at weblogic.rmi.cluster.ClusterableRemoteRef.readExternal(ClusterableRemoteRef.java:435)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:175)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:386)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.jndi.internal.BindingEnumeration.readExternal(BindingEnumeration.java:72)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:217)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jndi.internal.ServerNamingNode_922_WLStub.listBindings(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.listBindings(WLContextImpl.java:333)
at javax.naming.InitialContext.listBindings(InitialContext.java:406)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:105)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:134)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.jsptools.tree.JNDITreeHelper.printContext(JNDITreeHelper.java:48)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAct
Check that you do not have empty <jndi-name></jndi-name> tag in your database configuration files. Same problem happens on WLS10 if above empty tag present.
Similar Messages
-
Hi
I'm facing the following problem while viewing the JNDI tree. I had configured
two servers ejbServer,ejbServer1 both clustered, i can able to start both the
servers, but in the JNDI tree when i click ejbServer or Replication Manager
i'm getting the following error please help me out.
An unexpected error was encountered in processing your request.
Exception
javax.naming.NameNotFoundException: Unable to resolve weblogic.transaction.coordinators.ejbServer.
Resolved: 'weblogic.transaction.coordinators' Unresolved:'ejbServer' ; remaining
name ''
<>
Current Date
Mon Aug 27 09:15:19 GMT+08:00 2001
Console Release Build
6.0 Service Pack 2
Console Build
6.0 Service Pack 2 05/24/2001 11:55:28 #117037
Server Release Build
6.0 Service Pack 2
Server Build
6.0 Service Pack 2 05/24/2001 11:55:28 #117037
All Server Product Versions
WebLogic Server Build: 6.0 Service Pack 2 05/24/2001 11:55:28 #117037
WebLogic XML Module: 6.0 Service Pack 2 05/24/2001 12:34:27 #117037
Request Info
Protocol: HTTP/1.1
ServerName: 127.0.0.1
ServerPort: 7001
Secure: false
ContextPath: /console
ServletPath: /common/error.jsp
QueryString: null
PathInfo: null
PathTranslated: null
RequestURI: /console/common/error.jsp
AuthType: Basic
ContentType: null
CharacterEncoding: null
Locale: hi
Method: GET
Session: weblogic.servlet.internal.session.MemorySessionData@37b6ef
RequestedSessionId: O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q/console
RequestedSessionIdFromCookie: true
RequestedSessionIdFromURL: false
UserPrincipal: system
RemoteUser: system
RemoteAddr: 127.0.0.1
RemoteHost: localhost
Parameters
binding = ejbServer
context = weblogic.transaction.coordinators
Attributes
console.original./console/common/error.jsp.ContextPath = /console
console.original./console/common/error.jsp.Method = GET
console.original./console/common/error.jsp.RemoteUser = system
console.original./console/common/error.jsp.RequestURI = /console/common/error.jsp
console.original./console/common/error.jsp.ServletPath = /common/error.jsp
console.original./console/panels/mbean/JNDIBinding.jsp.ContextPath = /console
console.original./console/panels/mbean/JNDIBinding.jsp.Method = GET
console.original./console/panels/mbean/JNDIBinding.jsp.QueryString = context=weblogic.transaction.coordinators&binding=ejbServer
console.original./console/panels/mbean/JNDIBinding.jsp.RemoteUser = system
console.original./console/panels/mbean/JNDIBinding.jsp.RequestURI = /console/panels/mbean/JNDIBinding.jsp
console.original./console/panels/mbean/JNDIBinding.jsp.ServletPath = /panels/mbean/JNDIBinding.jsp
console.preferences.ContextKey = /panels/mbean/JNDIBinding.jsp
javax.servlet.include.context_path = /console
javax.servlet.include.request_uri = /console/common/requestinfo.jsp
javax.servlet.include.servlet_path = /common/requestinfo.jsp
javax.servlet.jsp.jspException = javax.naming.NameNotFoundException:
Unable to resolve weblogic.transaction.coordinators.ejbServer. Resolved: 'weblogic.transaction.coordinators'
Unresolved:'ejbServer' ; remaining name ''
weblogic.httpd.user = system
weblogic.management.console.tags.ContentTag = java.lang.Object@397a54
weblogic.management.console.tags.HeaderTag = java.lang.Object@e4a33
Headers
Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel,
application/msword, application/vnd.ms-powerpoint, */*
Accept-Encoding = gzip, deflate
Accept-Language = hi
Authorization = Basic c3lzdGVtOm1hbmFnZXIx
Connection = Keep-Alive
Cookie = JSESSIONID=O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q!2557472653882942880!-1062729946!7001!7002
Host = 127.0.0.1:7001
User-Agent = Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
BrowserInfo
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
IE: true
Netscape: false
Supported: true
JavscriptHrefs: false
TableCellClick: true
DocumentReloadedOnResize: false
DropdownStretchable: true
CellSpacingBlank: false
EmptyCellBlank: false
ImgOnclickSupported: true
TableBorderFancy: true
PartialToWideTables: false
Server System Properties
awt.toolkit = sun.awt.windows.WToolkit
bea.home = d:\Weblogic
cloudscape.system.home = ./samples/eval/cloudscape/data
file.encoding = Cp1252
file.encoding.pkg = sun.io
file.separator = \
java.awt.fonts =
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = .;d:\Weblogic\jdk130\lib\tools.jar;d:\Weblogic\wlserver\lib\weblogic_sp.jar;d:\Weblogic\wlserver\lib\weblogic.jar;d:\Weblogic\wlserver\lib\xmlx.jar;d:\Weblogic\wlserver\lib\ejb20.jar;d:\Weblogic\wlserver\samples\eval\cloudscape\lib\cloudscape.jar;;;;d:\Weblogic;d:\Weblogic\wlserver\bin\oci816_8;d:\Oracle_Home\iSuites\jdbc\lib\classes12.zip;d:\Weblogic\wlserver\lib;d:\Oracle_Home\iSuites\lib\xmlparserv2.jar;d:\JDeveloper\lib\xsu12.jar;;
java.class.version = 47.0
java.ext.dirs = d:\Weblogic\jdk130\jre\lib\ext
java.home = d:\Weblogic\jdk130\jre
java.io.tmpdir = C:\TEMP\
java.library.path = d:\Weblogic\jdk130\bin;.;C:\WINNT\System32;C:\WINNT;.\bin;D:\Oracle_Home\iSuites\BIN;D:\Oracle_Home\iSuites\Apache\Perl\5.00503\bin\mswin32-x86;C:\Program
Files\Oracle\jre\1.1.7\bin;C:\WINNT\system32;C:\WINNT;C:\VisualCafeSE\Java2\Bin;C:\Program
Files\Common Files\WebGain Shared;C:\VisualCafeSE\Bin;
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories
java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|weblogic.net|weblogic.utils
java.runtime.name = Java(TM) 2 Runtime Environment, Standard
Edition
java.runtime.version = 1.3.0-C
java.security.policy = =d:\Weblogic\wlserver/lib/weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.3
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
java.version = 1.3.0
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.3.0-C
javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
javax.xml.parsers.DocumentBuilderFactory = weblogic.xml.jaxp.RegistryDocumentBuilderFactory
javax.xml.parsers.SAXParserFactory = weblogic.xml.jaxp.RegistrySAXParserFactory
jmx.implementation.name = JMX RI
jmx.implementation.vendor = Sun Microsystems
jmx.implementation.version = 1.0
jmx.specification.name = Java Management Extensions
jmx.specification.vendor = Sun Microsystems
jmx.specification.version = 1.0 Final Release
line.separator =
os.arch = x86
os.name = Windows NT
os.version = 4.0
path.separator = ;
sun.boot.class.path = d:\Weblogic\jdk130\jre\lib\rt.jar;d:\Weblogic\jdk130\jre\lib\i18n.jar;d:\Weblogic\jdk130\jre\lib\sunrsasign.jar;d:\Weblogic\jdk130\jre\classes
sun.boot.library.path = d:\Weblogic\jdk130\jre\bin
sun.cpu.endian = little
sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx
pentium i486 i386
sun.io.unicode.encoding = UnicodeLittle
user.dir = D:\Weblogic\wlserver
user.home = C:\WINNT\Profiles\venkata
user.language = en
user.name = venkata
user.region = US
user.timezone = Asia/Singapore
weblogic.Domain = DNSdomain
weblogic.Name = DNSserver
weblogic.management.discover = true
weblogic.security.jaas.Configuration = weblogic.security.internal.ServerConfig
weblogic.security.jaas.Policy = d:/Weblogic/wlserver/lib/Server.policy
[att1.html]
-
Stack dump while trying to view the JNDI Tree on a managed server.
Hi,
We are running WLI 9.2.3.
I have a problem when trying to view the managed servers JNDI Tree via the Admin console. The admin servers JNDI tree appears to be fine, but trying to view the 1st managed servers JNDI Tree via the admin console keeps producing a stack dump.
Does anyone know why this would be? Is it a security issue, judging by the classes below:
####<Jul 14, 2010 1:31:29 PM BST> <Warning> <RMI> <sofatd2b> <tgri02_rsk_ms11> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel
<> <> <1279110689890> <BEA-080004> <An error was thrown by rmi server: weblogic.jndi.internal.RootNamingNode.listBindings(Ljava.lang.String;Ljava.util.Hashtable;)java.lang.StackOverflowError.
java.lang.StackOverflowError
at $Proxy5.isAccessAllowed(Unknown Source)
at com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed(AccessDecisionServiceImpl.java:105)
at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
at $Proxy11.isAccessAllowed(Unknown Source)
at com.bea.common.security.internal.service.AuthorizationServiceImpl.isAccessAllowed(AuthorizationServiceImpl.java:81)
at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
at $Proxy13.isAccessAllowed(Unknown Source)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:461)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:524)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:414)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:394)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:169)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)Hi,
if it works in Chrome then this Problem is related to IE.
Maybe the URL is to long? IE can "only" handle 2048 Characters.
Regards
-Seb. -
JNDI name is not displayed in server console JNDI tree
Hi. I have two objects with similar JNDI names. Object 1 has JNDI name "abc.test1". Object 2 has JNDI name "Abc.test2". Here is difference in first char size: 'a' and 'A'.
The issue is that in JNDI tree weblogic server console displays only Object 1. To see Object 2 I can change JNDI name for this object, but I do not want to change JNDI name.
Is there any way to see both objects without renaming Object 2?
I use WebLogic Server 8.1 SP4.
JNDI tree is displayed from console left panel: <domain>-<server>-<server name>-<right mouse click>-"View JNDI tree"Someone finally found this one (Farhan I think) - I hope you can find this link: its in this forum - just a few weeks old do a search on jndi on this forum if you don't find it.
http://forum.java.sun.com/thread.jsp?forum=136&thread=321971&start=15&range=15&hilite=false&q= -
Multiple WLS 4.5.1 processes using 1 single JNDI tree
Currently we are using 1 WLS process to deploy different beans in
our project. We know that all the deployed beans will be registered
within the JNDI service running in the context of this process.
But now we would like to change this configuration. We would like to
run more than 1 WLS processes deloying all different beans
which are using the same JNDI tree.
Example:
Process 1 delopys BEAN_A, BEAN_B ----> uses ------------
Process 2 delopys BEAN_C, BEAN_D --------------> JNDI Service Process
Process 3 delopys BEAN_E, BEAN_F ----> uses ------------
How can we do this?
Thanks
ChristophIf your WLS4.5.1 and WLS5.1 use different IP address, they can use the same
port. If they use the same IP address, they can not use the same port
number.
Cheers - Wei
Mark Ulmer <[email protected]> wrote in message
news:8gj41s$md5$[email protected]..
I understand that multiple instances of the WLS can be run on the samebox,
they are just listening on different ports. Does this still hold true ifI
am using a product that runs on top of WLS 4.5.1 and would like to have my
own WLS 5.1 instance running on the same box? Can this be done if I keep
the classpaths and weblogic_classpaths and all other related environment
settings seperate?
Thanks,
Mark Ulmer -
Summary of problem: Get a javax.naming.NamingNotFoundException when selecting the DataSource (see the configuration below) in server JNDI tree in Admin Console
TheConnection Pool and a corresponding DataSource are configured as follows:
<JDBCDataSource
JNDIName="jdbc.PNStoreDB"
Name="PNStoreDB"
PoolName="PNStorePool"
Targets="serverA"
/>
<JDBCConnectionPool
CapacityIncrement="2"
DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="2"
LoginDelaySeconds="1"
MaxCapacity="10"
Name="PNStorePool"
Properties="user=rms;password=rms;server=ora81"
RefreshMinutes="10"
Targets="serverA"
TestTableName="dual"
URL="jdbc:weblogic:oracle"
/>
Can't figure out why this is happening. The following is output to the Admin Server command prompt:
<May 18, 2001 10:20:02 AM EDT> <Error> <HTTP> <[WebAppServletContext(6233000,console)] exception raised on '/console/panel
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: '' Unresolved:'jdbc' ; remaining name ''
<<no stack trace available>>
I tried using a different JNDI name for the DataSource (e.g. just PNStoreDB) with no success.
The weird thing is that it messes up other resources bound in the JNDI tree. For e.g. I have some EJB's bound under ejb/XXXX that I can click on and view in the Admin Console (JNDI tree) before I add the pool and DataSource. After I add them though, I see the same NameNotFoundException for these as well.
Thanks in advance for your help.
[att1.html]Are you sure that the connection pool and datasource deployed
successfully? (Check the logs for an error.)
Also, I suspect that you want a TxDataSource instead of a
JDBCDataSource.
-- Rob
Weblogic NewsGroups wrote:
Summary of problem: Get a javax.naming.NamingNotFoundException when
selecting the DataSource (see the configuration below) in server JNDI
tree in Admin Console
TheConnection Pool and a corresponding DataSource are configured as
follows:
<JDBCDataSource
JNDIName="jdbc.PNStoreDB"
Name="PNStoreDB"
PoolName="PNStorePool"
Targets="serverA"
/>
<JDBCConnectionPool
CapacityIncrement="2"
DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="2"
LoginDelaySeconds="1"
MaxCapacity="10"
Name="PNStorePool"
Properties="user=rms;password=rms;server=ora81"
RefreshMinutes="10"
Targets="serverA"
TestTableName="dual"
URL="jdbc:weblogic:oracle"
/>
Can't figure out why this is happening. The following is output to
the Admin Server command prompt:
<May 18, 2001 10:20:02 AM EDT> <Error> <HTTP>
<[WebAppServletContext(6233000,console)] exception raised on
'/console/panel
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved:
'' Unresolved:'jdbc' ; remaining name ''
<<no stack trace available>>
I tried using a different JNDI name for the DataSource (e.g. just
PNStoreDB) with no success.
The weird thing is that it messes up other resources bound in the JNDI
tree. For e.g. I have some EJB's bound under ejb/XXXX that I can
click on and view in the Admin Console (JNDI tree) before I add the
pool and DataSource. After I add them though, I see the same
NameNotFoundException for these as well.
Thanks in advance for your help.--
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com -
Hello,
I work with Weblogic server 9.2 and Ganymede 3.4.
Here are some beginner questions:
Why do I, in Ganymede's server tab, publish on the server node instead of on the EAR node?
When I publish my EAR I cannot see anything added in the jndi tree of the app-server (via admin console, view jndi tree). What do I miss?
This my weblogic-ejb-jar:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<!-- server-version: 9.2 -->
<weblogic-enterprise-bean>
<ejb-name>HelloWorld</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<jndi-name>ejb.EjbHelloWorldHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Is there a perspective that displays the weblogic generated stub/skeleton files?
Is there a difference between publishing an EAR and deploying an EAR, except that deploying refers to a production environment instead of dev environment?
Thanks for any ideas.If you are using OEPE - Oracle Enterprise Pack for Eclipse (or Workshop), then WebLogic EJB's are built (the stubs, etc) with a tool called EJBGen, this link is for 10.3, but I'm pretty sure it's the same for 9.2
http://download.oracle.com/docs/cd/E12839_01/wls/docs103/ejb/EJBGen_reference.html
I think that is implemented as a an Eclipse build task, so it's only run when exporting to an archive like an EAR or EJB jar OR when publishing to the server. In either case, those generated classes would not be shown in Eclipse.
Check your deployments tab of your WLS console to see if you application is deployed an active. If it is, then I would expect to see entries from your application in the JNDI tree.
The OEPE forum is a better place to ask Eclipse questions:
Enterprise Pack for Eclipse -
EJB deployed but doesnt show up in JNDI tree on weblogic
Hi,
I have a sample EJB deployed on weblogic 10.3 server. My Bean class contains following code.
========================================================================
@Stateless (mappedName = "DemoEJB")
@TransactionManagement(TransactionManagementType.BEAN)
public class DemoBean implements SessionBean {
static final boolean verbose = true;
private transient SessionContext ctx;
private transient Properties props;
@SuppressWarnings("deprecation")
@Override
public void setSessionContext(SessionContext ctx) throws EJBException,
RemoteException {
// TODO Auto-generated method stub
if (verbose)
System.out.println("setSessionContext called");
this.ctx = ctx;
props = ctx.getEnvironment();
public String demoSelect()
throws RemoteException
return("hello world");
===========================================================================
I have created a jar file for the above class using eclipse and deployed it on weblogic. I can see the EJB in the <Deployment> on weblogic but it doesnt appear in <EJB> on JNDI tree view. Therefore i cannot access it from my client code (also written in Eclipse IDE).
I will appreciate any guidance in this regard.
Thanks
Regards,
AwaisHi,
i have the same problem with yours
This is my annotation with EJB3.0:
@Stateless(mappedName="ConSession")
@Remote(ConBeanRemote.class)
@Local(ConBean.class)
and i have a weblogic-ejb-jar.xml to define my jndi name
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-ejb-jar"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd
http://www.bea.com/ns/weblogic/weblogic-ejb-jar
http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>ConSession</ejb-name>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>com.staffware.ConBeanRemote</business-remote>
<jndi-name>ConSession#com/staffware/ConBeanRemote</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
<local-jndi-name>com/ConfigurationManagerBeanLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
[ the most important： I also have specify JNDI in a java file like this
beanRemoteJNDIs.put("ConBeanRemote","ConSession#com/staffware/ConBeanRemote");
beanLocalJNDIs.put("ConBean","java:comp/env/com/ConBean");
and i can find the ConSession#com/staffware/ConBeanRemote in the jndi tree . but it shows like Multilevel directory tree
and when i login the website and click the button
.another error comes out :
13:35:55,046 ERROR [EJBDelegate] Unable to lookup reference java:comp/env/com/ConBean for ConBean!
javax.naming.LinkException: [Root exception is javax.naming.LinkException: [Root exception is javax.naming.NameNotFoun
dException: While trying to look up /app/ejb/CONFIG-ejb-2.0.jar#ConSession/local-home in /app/webapp/CO
M/18328287.; remaining name '/app/ejb/CONFIG-ejb-2/0/jar#ConfigurationManagerSession/local-home']; Link Remaining Name:
'java:app/ejb/CONFIG-ejb-2.0.jar#ConSession/local-home']; Link Remaining Name: 'com/ConBean'
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:104)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:884)
at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:187)
what should i do ?
and should i specify the jndi name in the java file . the JNDI name defined in the weblogic is right?
can you help me ?
thanks very much in advance! -
"View JNDI tree" link not visible under monitoring tab of myserver?
Hi,
The link "View JNDI tree" as mentioned in chapter 18 of administration guide is
not visibile on my installation of 6.1 beta.
Is there some configuration setting that i need to do to make this link visible.
I am having problems with installation and running of my resource adapter. I wanted
to check whether the JNDI name is registered properly and there i ran into this
problem of no link available.
Regards
ManishThey moved this into a popup menu that you get to using a right click
in the tree view in the left frame. There are lots and lots of new
admin goodies available by right clicking on nodes of the tree. It
took me a while to discover this myself. :)
Ben
On 20 Jun 2001 10:29:12 -0800, Manish Verma <[email protected]> wrote:
>
The link "View JNDI tree" as mentioned in chapter 18 of
administration guide is not visibile on my installation of 6.1 beta. -
Adapter JNDI are errored out in JNDI tree on Weblogic
Hey,
I have setup weblogic 10.3.4 and SOA Suite 11g.
The adapters seem to be deployed and active with a green 'OK' status in the deployments on the soa_server1. However when I go to the jndi tree for the soa_server1, all the adapters have an '!' for errored out.
This is causing various problems. In particular when a process using the Oracle Apps Adapter is deployed it is unable to find the jdbc connection associated with the adapter. However, the jdbc jndi entry is in the tree and the jdbc connection test's just fine.
So there seems to be a missing link in how the adapters are deployed and how the JNDI is getting updated or something.
The error is below. Any help appreciated.
====> CubeEngine load MIS_INB_WorkOrder_AR_Sync/Process_WO_AR_Sync took 726 ms
INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/MIS_INB_WorkOrder_AR_Sync!1.0*soa_85dcf1de-1d63-4b34-9f99-3e52c1f04366
<Aug 10, 2011 1:25:33 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
INFO: SchemaManager.isIncrementalBuildSupported XMLSchema incremental build enabled.
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync Error while performing endpoint Activation: javax.resource.ResourceException: Unable to find data source null>
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync
javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
... 26 more
>
oracle.fabric.common.FabricDeploymentException: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
{rootCauses=[]}
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:66)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:608)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: BINDING.JCA-12517
Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:513)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
... 11 more
Caused by: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
... 15 more
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
... 26 more
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "MIS_INB_WorkOrder_AR_Sync" failed: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.Hey,
I have setup weblogic 10.3.4 and SOA Suite 11g.
The adapters seem to be deployed and active with a green 'OK' status in the deployments on the soa_server1. However when I go to the jndi tree for the soa_server1, all the adapters have an '!' for errored out.
This is causing various problems. In particular when a process using the Oracle Apps Adapter is deployed it is unable to find the jdbc connection associated with the adapter. However, the jdbc jndi entry is in the tree and the jdbc connection test's just fine.
So there seems to be a missing link in how the adapters are deployed and how the JNDI is getting updated or something.
The error is below. Any help appreciated.
====> CubeEngine load MIS_INB_WorkOrder_AR_Sync/Process_WO_AR_Sync took 726 ms
INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/MIS_INB_WorkOrder_AR_Sync!1.0*soa_85dcf1de-1d63-4b34-9f99-3e52c1f04366
<Aug 10, 2011 1:25:33 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
INFO: SchemaManager.isIncrementalBuildSupported XMLSchema incremental build enabled.
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync Error while performing endpoint Activation: javax.resource.ResourceException: Unable to find data source null>
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync
javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
... 26 more
>
oracle.fabric.common.FabricDeploymentException: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
{rootCauses=[]}
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:66)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:608)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: BINDING.JCA-12517
Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:513)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
... 11 more
Caused by: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
... 15 more
Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
... 19 more
Caused by: javax.resource.ResourceException: Unable to find data source null
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
... 22 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
... 26 more
<Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "MIS_INB_WorkOrder_AR_Sync" failed: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process.
: Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
Please correct the reported issue and redeploy the BPEL process. -
Are workmanagers visible in the jndi tree viewer?
Hi, I'm trying to setup a workmanager, and I'm having a few problems, but I'm just wondering if I'm falling at the first hurdle. I've tried creating workmanagers at the global and application level, but looking in the admin console for my server they never show up in the jndi tree viewer. Should I expect to see my workmanager there? If I look in the deployment then I do see that the workmanager exists, alongside default.
Thanks.If you create a workmanager at the application level, you'll see the work manager in the console under Deployments -> your app -> Monitoring ->Workload.
If you create a workmanager at the domain / server level and reference it within your app's deployment descriptors ( wl-dispatch-policy ), you can look under Servers ->your app's targeted server -> Deployments -> your app -> Monitoring -> Workload. In this case, you'll see all the workmanagers targeted to that server, but you can confirm your app's usage of the correct wm by submitting a request to your app and seeing an increase in the completed requests column of the display.
A work manager configured at the domain / server level doesn't have a JNDI name attribute that you enter. You just use the same workmanager name in your deployment descriptor <wl-dispatch-policy>someWM</wl-dispatch-policy>.
The handling of stuck threads seems to be a trouble point for application defined workmanagers, so we've decided to stick with individual server level work managers for each app. -
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 BedardYes, 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 -
ACL on JNDI tree or elements in it
Hello
I am trying to find out how I can secure information in the JNDI tree.
The documentation led me to believe using the t3 naming service I could
protect anything under acl.<i>perm</i>.weblogic.jndi.<i>path</i>
but this does not seem to be the case. I assumed path was the jndi
path name... I have been unable to find documentation on what I
can attach ACL to in the JNDI tree - though I have seen a few
posted on deja, example from filerealm.properties,
#acl.list.weblogic.jndi.weblogic.ejb=system
#acl.modify.weblogic.jndi.weblogic.rmi=system
#acl.lookup.weblogic.jndi.weblogic.fileSystem=system
There seems to be <b>no</b> definitive list though in the BEA documentation.
Can anyone refer me to docs on what JNDI elements can attach ACL?
Or how I can protect things in the JNDI tree? I get the impression,
that I must manually implement ACL support for remote objects
I add into the tree. I have also not found good information
on this.
not helpful
anything searched with JNDI and ACL
http://e-docs.bea.com/wls/docs61/adminguide/cnfgsec.html
not very helpful
http://e-docs.bea.com/wls/docs61/security/prog.html#1043942Hi,
Check this debug in ur environment.
-Dweblogic.jndi.retainenvironment=true
this should show you the path.
Regards,
Kal. -
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.
>>
>
>
Maybe you are looking for
-
Clarification of the handle/body idiom in multi threaded applications
Hello As some DBXML classes use the handle-body idiom (handle/body idiom in some docs), could someone please clarify the consequences of that in a multi threaded application like a web container? For 100% Java people, like me, this is known in the Ja
-
Hello, I'm new to the forums I just started learning flash a few days ago and i am LOVING it! I already started work ona a website, but I need some help. In my website I want to have a few pictures where if you move your mouse over them they show you
-
alright so i tried out my friends iphone and i gotta say its pretty stinkin sweet and im thinkin abt gettin one around christmas but i see that there is 2 different memory capacities the 4 and 8 GB. so which one is better. i have and ipod (30GB) so i
-
BOMUpdate WebService times out
Hi, When I am running the BOMUpdate web-service with a BOM containing 1771 Bom components it times out after 10 minutes. A BOM Update with 1071 components does not time out, but anyway take about 4 minutes to finish. Have anybody experience with BOM
-
Best GPS software w/external puck and Verizon?
For years I've used WM phones with an external gps receiver (i.trek M series) and iGuidance software. It worked fantastic. Now I've been forced to switch to a BB Curve running on Verizon. I still have my i.trek M5 but don't know the best software