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
Similar Messages
-
Binding huge object to the jndi tree.
Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. This same thing is working with about 4MB object in Sun One but takes about 45 Mins to 1 Hour to finish the serialization etc for jndi .Kindly provide some guidance.Thanks in advance.
True. At the end I configured the value as a "server property". The cool thing about configuring the jndi tree is that it is replicated in a cluster.
Obviously the values that I inserted affected all the applications, like the url of our SOA server. -
Adding entries to the JNDI tree
Is it possible to add entries to the JNDI path of the OC4J server? I know you can add it via web.xml, but I´m looking into doing that manually through the admin console?
Thanks,
MarioTrue. At the end I configured the value as a "server property". The cool thing about configuring the jndi tree is that it is replicated in a cluster.
Obviously the values that I inserted affected all the applications, like the url of our SOA server. -
AS7.0b:JMS: can I browse the JNDI tree with the admin tool?[cid:792813]
Is there a way to browse the JNDI Tree thru the Admin Tool.
1) I have deployed a Topic Destination with the name jms/AuditTopic,
jms/MonitorTopic
2) I have deployed a MDB with the name AuditAgent which is tied to
jms/AuditTopic
when the server is deploying the AuditAgent MDB it throws the following
error:
INFO: JMS5002: Binding [< JMS Destination: jms/MonitorTopic,
javax.jms.Topic, No properties >]
SEVERE: JMS5027: Exception in creating JMS destination administered object
[jms/MonitorTopic]: [[A4017]: Destination name is not specified.]
SEVERE: JMS5031: Exception in creating JMS destination administered object
javax.jms.JMSException: [A4017]: Destination name is not specified.
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.createDestinationObject(JMSAdminImpl.java:193)
at com.iplanet.ias.jms.IASJmsConfig.createDestination(UnknownSource)
at com.iplanet.ias.jms.IASJmsUtil.installJMSResources(UnknownSource)
at com.sun.enterprise.resource.ResourceInstaller.installJMSResources(UnknownSource)
at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onInitialization(UnknownSource)
at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
INFO: JMS5002: Binding [< JMS Destination: jms/AuditTopic, javax.jms.Topic,
No properties >]
SEVERE: JMS5027: Exception in creating JMS destination administered object
[jms/AuditTopic]: [[A4017]: Destination name is not specified.]
SEVERE: JMS5031: Exception in creating JMS destination administered object
javax.jms.JMSException: [A4017]: Destination name is not specified.
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.createDestinationObject(JMSAdminImpl.java:193)
at com.iplanet.ias.jms.IASJmsConfig.createDestination(UnknownSource)
at com.iplanet.ias.jms.IASJmsUtil.installJMSResources(UnknownSource)
at com.sun.enterprise.resource.ResourceInstaller.installJMSResources(UnknownSource)
at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onInitialization(UnknownSource)
at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
INFO: JMS5002: Binding [< JMS Connection Factory:
jms/TopicConnectionFactory, javax.jms.TopicConnectionFactory, No properties>]
FINE: ++++ Entered SecClientRequestInterceptor::send_request()
SEVERE: NAM5005: JMS Destination object not found: jms/AuditTopic
SEVERE: javax.naming.NameNotFoundException
javax.naming.NameNotFoundException: AuditTopic not found
at com.sun.enterprise.naming.TransientContext.doLookup(Unknown Source)
at com.sun.enterprise.naming.TransientContext.lookup(Unknown Source)
at com.sun.enterprise.naming.TransientContext.lookup(Unknown Source)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(Unknown Source)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(Unknown Source)
at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
at com.sun.enterprise.naming.SerialContext.lookup(Unknown Source)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(Unknown Source)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(Unknown Source)
at com.sun.ejb.containers.BaseContainer.<init>(Unknown Source)
at com.sun.ejb.containers.MessageBeanContainer.<init>(Unknown Source)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Unknown Source)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
SEVERE: EJB5016: Exception creating BaseContainer :
[javax.naming.InvalidNameException: JMS Destination object not
found:`jms/AuditTopic`]
FINE: EJB5016: Exception creating BaseContainer : [{0}]
javax.naming.InvalidNameException: JMS Destination object not
found:`jms/AuditTopic`
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(Unknown Source)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(Unknown Source)
at com.sun.ejb.containers.BaseContainer.<init>(Unknown Source)
at com.sun.ejb.containers.MessageBeanContainer.<init>(Unknown Source)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Unknown Source)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
SEVERE: EJB5090: Exception in creating EJB container
[javax.naming.InvalidNameException: JMS Destination object not
found:`jms/AuditTopic`]
WARNING: LOADER5004: UnExpected error occured while creating ejb container
javax.naming.InvalidNameException: JMS Destination object not
found:`jms/AuditTopic`
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(Unknown Source)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(Unknown Source)
at com.sun.ejb.containers.BaseContainer.<init>(Unknown Source)
at com.sun.ejb.containers.MessageBeanContainer.<init>(Unknown Source)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Unknown Source)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
FINE:
org.omg.CORBA.OBJ_ADAPTER: NoContext: outside of an invocation context.
vmcid: 0x0 minor code: 0 completed: No
at com.sun.corba.ee.internal.POA.DelegateImpl.poa(Unknown Source)
at org.omg.PortableServer.Servant._poa(Servant.java:99)
at com.rai.common.inbound._InboundManagerBean_EJBObjectImpl_Tie.deactivate(Unknown Source)
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.cleanUpTie(Unknown Source)
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.unexportObject(Unknown Source)
at javax.rmi.CORBA.Util.unexportObject(Util.java:159)
at com.sun.enterprise.iiop.POAProtocolMgr.destroyReference(Unknown Source)
at com.sun.ejb.containers.StatelessSessionContainer.undeploy(Unknown Source)
at com.iplanet.ias.server.AbstractLoader.unloadEjbs(Unknown Source)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
3)Some extra error and warnings follow:
FINE: No SAS context element found in service context list
WARNING:
java.io.IOException: Invalid indirection to offset 2940
at com.sun.corba.se.internal.io.IIOPInputStream.throwExceptionType(Native Method)
at com.sun.corba.se.internal.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:274)
at com.sun.corba.se.internal.io.ValueHandlerImpl.readValueInternal(ValueHandlerImpl.java:247)
at com.sun.corba.se.internal.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:209)
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(Unknown Source)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(Unknown Source)
at com.sun.corba.ee.internal.corba.TCUtility.unmarshalIn(Unknown Source)
at com.sun.corba.ee.internal.corba.AnyImpl.read_value(Unknown Source)
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_any(Unknown Source)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_any(Unknown Source)
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.readAny(Unknown Source)
at javax.rmi.CORBA.Util.readAny(Util.java:90)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(Unknown Source)
at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResource(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResources(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(Unknown Source)
at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onInitialization(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
FINE:
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Invalid
indirection to offset 2940 vmcid: SUN minor code: 211 completed: Maybe
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(Unknown Source)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(Unknown Source)
at com.sun.corba.ee.internal.corba.TCUtility.unmarshalIn(Unknown Source)
at com.sun.corba.ee.internal.corba.AnyImpl.read_value(Unknown Source)
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_any(Unknown Source)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_any(Unknown Source)
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.readAny(Unknown Source)
at javax.rmi.CORBA.Util.readAny(Util.java:90)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(Unknown Source)
at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResource(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResources(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(Unknown Source)
at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onInitialization(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
FINE: ++++ Entered SecClientRequestInterceptor::receive_exception
SEVERE: RSR5049:Error publishing JDBC connection Pool Resource
javax.naming.CommunicationException: java.rmi.MarshalException: CORBA
MARSHAL 1398079699 Maybe; nested exception is:
org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 211 completed:
Maybe
at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResource(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResources(Unknown Source)
at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(Unknown Source)
at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
at com.iplanet.ias.server.ApplicationServer.onInitialization(Unknown Source)
at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
FINE: ++++ Entered SecClientRequestInterceptor::send_request()
FINE: Security context is null (nothing to add to service context)
FINE: No SAS context element found in service context listHi Rohit,
Thanks for your response..
Below is the BLAdminTopic configuration.Please let me know if you need any further info.
Topic:BLAdminTopic
Type:Distributed Topic
JNDI:jms/BLAdminTopic
Sub Deployment :N/A
Target:N/A
BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
Regards,
Jyotiranjan -
Hi
I am just a starter on WLPortal.
I have created a barebone Application from scratch. I have synchronized it properly
from EBCC to WLP. But When I am trying to access the home page of my application,
I am getting from stack trace -
<Nov 6, 2002 5:37:59 PM IST> <Error> <PortalAppflow> <Could not lookup PortalManagerHome
in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager.
javax.naming.NameNotFoundException: Unable to resolve comp/env/ejb/PortalManager
Resolved: 'comp/env' Unresolved:'ejb' ; remaining name 'PortalManager'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:802)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:173)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:181)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:181)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:36)
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at com.bea.p13n.util.JndiHelper.lookupNarrow(JndiHelper.java:96)
at com.bea.portal.appflow.PortalAppflowHelper.<clinit>(PortalAppflowHelper.java:64)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.init(PortalWebflowServlet.java:78)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:700)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:643)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:588)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:368)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:215)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2459)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Nov 6, 2002 5:37:59 PM IST> <Error> <HTTP> <[WebAppServletContext(19695286,FirstWebApp,/FirstWebApp)]
Servlet failed with Exception
java.lang.NullPointerException:
at com.bea.portal.appflow.PortalAppflowHelper.createPortalManager(PortalAppflowHelper.java:82)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalRequest(PortalWebflowServlet.java:187)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:215)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2459)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
When I decompiled the class PortalAppflowHelper, I found a static block in it,
which was as under-
static
debug = Debug.getInstance(com.bea.portal.appflow.PortalAppflowHelper.class);
try
if(debug.ON)
debug.out("Looking up PortalManagerHome using EJB reference java:comp/env/ejb/PortalManager");
portalManagerHome = (PortalManagerHome)JndiHelper.lookupNarrow("java:comp/env/ejb/PortalManager",
com.bea.portal.manager.ejb.PortalManagerHome.class);
if(debug.ON)
debug.out("Successfully retrieved PortalManagerHome " + portalManagerHome);
catch(Exception e)
PortalAppflowLogger.errorFindingPortalManagerHome("java:comp/env/ejb/PortalManager",
e);
I have checked the PortalManager's JNDI name on WLConsole. Its ${APPNAME}.BEA_portal.PortalManager.
Should I change it?
When I tried to change it, I started getting other weird errors.
Thanks
Neeraj HansNeeraj -
The Portal framework code (including PortalAppflowHelper) uses ejb
references to find the PortalManager (and other EJBs) from servlets and
taglibs; that is what is signified by the java:comp/env/... name.
Since you built your webapp from scratch (instead of using the portal
wizard), you will need to make sure the you have the appropriate
<ejb-ref> entries in your web.xml, and the corresponding
<ejb-reference-description> entries in your weblogic.xml. By default,
you will need at least mappings for:
- ejb/PortalManager
- ejb/UserManager
- ejb/GroupManager
- ejb/PipelineExecutor
- ejb/EventService
See either the resulting webapp from using the portal wizard or
BEA_HOME/weblogic700/samples/portal/sampleportalDomain/beaApps/sampleportal/sampleportal/WEB-INF
for example syntax.
Greg
Neeraj Hans wrote:
Hi
I am just a starter on WLPortal.
I have created a barebone Application from scratch. I have
synchronized it properly
from EBCC to WLP. But When I am trying to access the home page of my
application,
I am getting from stack trace -
<Nov 6, 2002 5:37:59 PM IST> <Error> <PortalAppflow> <Could not lookup
PortalManagerHome
in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager.
javax.naming.NameNotFoundException: Unable to resolve
comp/env/ejb/PortalManager
Resolved: 'comp/env' Unresolved:'ejb' ; remaining name 'PortalManager'
at <stack trace lines snipped>
When I decompiled the class PortalAppflowHelper, I found a static
block in it,
which was as under-
static
debug =
Debug.getInstance(com.bea.portal.appflow.PortalAppflowHelper.class);
try
if(debug.ON)
debug.out("Looking up PortalManagerHome using EJB
reference java:comp/env/ejb/PortalManager");
portalManagerHome =
(PortalManagerHome)JndiHelper.lookupNarrow("java:comp/env/ejb/PortalManager",
com.bea.portal.manager.ejb.PortalManagerHome.class);
if(debug.ON)
debug.out("Successfully retrieved PortalManagerHome "
+ portalManagerHome);
catch(Exception e)
PortalAppflowLogger.errorFindingPortalManagerHome("java:comp/env/ejb/PortalManager",
e);
I have checked the PortalManager's JNDI name on WLConsole. Its
${APPNAME}.BEA_portal.PortalManager.
Should I change it?
When I tried to change it, I started getting other weird errors.
Thanks
Neeraj Hans -
EJB not published in the JNDI tree
I am trying to deploy a simple ear file containing one ejb on to WL 9.2. The app is deploying without any problems, but the EJB is not published in the JNDI tree. When I look at the EJB's configuration through the admin console, it does indicated that the JNDI name is set to "ejb/HelloWorld". However, when I look at the JNDI tree there is no HelloWorld node under ejb. Below is my weblogic-ejb-jar.xml file that defines the JNDI name:
<?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">
<weblogic-enterprise-bean>
<ejb-name>HelloWorld</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>1000</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>0</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>false</enable-call-by-reference>
<jndi-name>ejb/HelloWorld</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>Can anyone help me understand why the JNDI name is not being published?
Thanks.Hi all,
It seems that I have the same problem with WL 10. Has any of you solved this yet?
I'm trying to switch my application from perfectly working JBoss 4.2 environment to WL 10 and no luck so far, because of this weird problem.
What I have noticed so far is:
- Some of my sessions beans are deployed ok
- "Big" session beans are silently ignored in deployment. This is unbelievable because these beans are SILENTLY ignored. And, my session beans are not that big. Under 700 LOC all of them.
- These EJBs don't appear in admin console's JNDI-browser
- These EJBs don't appear in ear-content details in "Deployments" section.
- These EJBs don't get their stubs generated in server/cache/EJBCompilerCache
- One big is ignored, but when splitting it in e.g. three smaller ones, all of these three session beans are deployed successfully
I'm using EJB3 session beans with no XML-descriptors.
So what is going on here??!
Looking forward to hear some answers. At least from BEA developers or other insiders.
Thanks.
Edited by villeingman at 06/13/2007 12:42 AM -
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. -
Localhome doesnot appear on the jndi tree on weblogic 8.1 after deployment
I am upgrading my application from weblogic6.1 to weblogic 8.1 sp3.
I have a stateless session bean with local interfaces. when I deploy the bean to the weblogic 8.1 server, everything seems to be fine and no error occurs. but when I view the JNDI tree, the localhome is not there and the local interface has just the Bind Name and no stub, no object hash code, no object class and no object to string appears. Trying to test the EJB in the console I get the following error:
"The EJB MeldePersonDatabaseFacadeBean has not been tested successfully. There was a problem determining the JNDI Name of the given bean."
what's wrong? why does not local interfaces deploy correctly on weblogic 8.1?
my descriptors are as follows:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<display-name>MeldePersonDatabaseEJB</display-name>
<enterprise-beans>
<session>
<display-name>MeldePersonDatabaseFacadeBean</display-name>
<ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
<local-home>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocalHome</local-home>
<local>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocal</local>
<ejb-class>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
<local-jndi-name>MeldePersonDatabaseFacadeBeanLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
--------------------I believe the console only supports testing of remote ejbs.
I didn't see anything obviously wrong with your app. I'm guessing that
it's working fine. I'd just write a Servlet that hits the local ejb.
That should prove whether it's working or not.
-- Rob
Murteza Salemi wrote:
I am upgrading my application from weblogic6.1 to weblogic 8.1 sp3.
I have a stateless session bean with local interfaces. when I deploy the bean to the weblogic 8.1 server, everything seems to be fine and no error occurs. but when I view the JNDI tree, the localhome is not there and the local interface has just the Bind Name and no stub, no object hash code, no object class and no object to string appears. Trying to test the EJB in the console I get the following error:
"The EJB MeldePersonDatabaseFacadeBean has not been tested successfully. There was a problem determining the JNDI Name of the given bean."
what's wrong? why does not local interfaces deploy correctly on weblogic 8.1?
my descriptors are as follows:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<display-name>MeldePersonDatabaseEJB</display-name>
<enterprise-beans>
<session>
<display-name>MeldePersonDatabaseFacadeBean</display-name>
<ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
<local-home>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocalHome</local-home>
<local>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocal</local>
<ejb-class>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
<local-jndi-name>MeldePersonDatabaseFacadeBeanLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar> -
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. -
ASControl JNDI Browser not displaying the JNDI tree (10.1.3.2)
We're running OC4J 10.1.3.2 on JDK 1.5.0_06
We have a problem that when we try to access the JNDI Browser on any of the instances that we have created,
the JNDI Browser always displays "No Properties Found".
I have created an instance named "web" and the default "home" instance exists. ASControl is running in the home instance.
When we access the JNDI Browser in the home instance, everything works correctly.
When I access the JNDI Browser in the web instance through ASControl, I see the following exception in the opmn/logs/default_group~home~default_group~1.log,
07/05/23 09:55:22 java.lang.UnsupportedOperationException: This part of the API is not supported
07/05/23 09:55:22 at oracle.oc4j.admin.jmx.distributed.SimpleInstanceMBeanServerDelegate.queryMBeans(SimpleInstanceMBeanServerDelegate.java:522)
07/05/23 09:55:22 at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.queryMBeans(LocalizationFilterMBeanServer.java:420)
07/05/23 09:55:22 at oracle.sysman.ias.studio.jmx.spi.JMXConnectorImpl.queryMBeans(JMXConnectorImpl.java:346)
07/05/23 09:55:22 at oracle.sysman.ias.studio.j2ee.userdefined.jndi.JndiHGridOC4JModel.getJndiTree(JndiHGridOC4JModel.java:164)
07/05/23 09:55:22 at oracle.sysman.ias.studio.j2ee.userdefined.jndi.JndiHGridOC4JModel.getJndiTree(JndiHGridOC4JModel.java:134)
07/05/23 09:55:22 at oracle.sysman.ias.studio.j2ee.userdefined.jndi.JndiGridHelper.createHGrid(JndiGridHelper.java:421)
07/05/23 09:55:22 at oracle.sysman.ias.studio.j2ee.userdefined.jndi.JndiGridHelper.prepareData(JndiGridHelper.java:357)
07/05/23 09:55:22 at oracle.sysman.ias.studio.sdk.AbstractController.prepareData(AbstractController.java:875)
07/05/23 09:55:22 at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:391)
07/05/23 09:55:22 at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:765)
07/05/23 09:55:22 at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:283)
07/05/23 09:55:22 at oracle.sysman.ias.studio.app.StudioConsole.doGet(StudioConsole.java:297)
07/05/23 09:55:22 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
07/05/23 09:55:22 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
07/05/23 09:55:22 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
07/05/23 09:55:22 at oracle.sysman.ias.studio.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:75)
07/05/23 09:55:22 at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
07/05/23 09:55:22 at oracle.sysman.ias.studio.app.MultipleJVMFilter.doFilter(MultipleJVMFilter.java:85)
07/05/23 09:55:22 at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
07/05/23 09:55:22 at oracle.sysman.ias.studio.app.PostLogonFilter.doFilter(PostLogonFilter.java:80)
07/05/23 09:55:22 at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
07/05/23 09:55:22 at oracle.sysman.ias.studio.app.ShortHostnameRedirectFilter.doFilter(ShortHostnameRedirectFilter.java:68)
07/05/23 09:55:22 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:620)
07/05/23 09:55:22 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
07/05/23 09:55:22 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
07/05/23 09:55:22 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
07/05/23 09:55:22 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
07/05/23 09:55:22 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
07/05/23 09:55:22 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
07/05/23 09:55:22 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
07/05/23 09:55:22 at java.lang.Thread.run(Thread.java:595)
In the web instance, if I invoke the "getAllBindingsAsXMLString" operation on the oc4j/J2EEServer/JNDINamespace/JNDINamespace node through the system MBean browser, I can then see the contents of the JNDI.
Any help with this problem would be greatly appreciated.I have the same problem.
Also on OC4J 10.1.3.2 and JDK 1.5.0_06
Any help would be welcome -
Looking up an object that isn't in the JNDI tree
We currently have this current hypothesis. Could someone verify this?
If you make a call using JNDI and try to retrieve something that's not
registered ("com.foobar.weblogic.SomeClass"), it will be dynamically
instantiated and returned, as long as the requested class is
a) in the SERVERCLASSES directory, and
b) has a no-arg constructor.Just closing the case.
Next time I ran the battery down and plugged it back in, everything is working as if the problem never happened. Not sure what I did wrong the first time. -
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();
KomalIf 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 -
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.
>>
>
>
-
Refresh JNDI tree when accessing from outside the container
Hello,
I wrote a tool (a simple main class) which runs a thread to simply check the DataSources stored in an Application Server's JNDI tree (to see, if they can be used by other tools).
The problem is: Once the thread is running, it always gets the same DataSource back, no matter if the DS's properties changed. Let me describe what happens:
1. I defined a DataSource in Orion 2.0.5's data-sources.xml
2. Testing it with an application in the container works fine.
3. I start my external tool, which gets the DataSource and checks it - it works
4. Then I stop the container and change the DataSource props in a way that the connection won't be established (i.e. wrong url)
5. After restarting the container, the aplication in the container throws the expected SQLException
6. But the external tool (which is still running) does its next lookup for the DataSource and gets a valid one and claims that everything is fine.
Well, it seems to me that the external tool outside of the container somehow gets a copy of the JNDI tree (or something) and does no real lookup, but I just don't know. Another hint is, that - unless I do a context.list(""); before looking up the object - the container did not even need to run after the first lookup from the external tool - it just needed one lookup and afterwards I could stop the container without having the external tool recognizing any changes. Well, it at least recognizes that now by the above mentioned context.list(""); ...
I hope I explained it right, let me just add some code of my tool.
Thank you in advance for any hints!
Greetings, Sebastian
//only the important stuff...
public class DataSourceChecker extends Thread {
/** The array with the names of the data sources (command line args)). */
private String[] _datasourceNames;
/** Defines in seconds how long the thread sleeps. */
private int _sleepSeconds;
public void run() {
boolean success;
while (true) {
//check each datasource...
success = true;
for (int i = 0; i < _datasourceNames.length; i++) {
if (!isDataSourceValid(_datasourceNames)) {
success = false;
break;
writeFile(success);
try {
sleep(_sleepSeconds * 1000);
} catch (InterruptedException ie) {
_log.error("Error while trying to put thread to sleep.");
private boolean isDataSourceValid(String dataSource) {
DataSource ds = null;
Connection con = null;
boolean success = true;
try {
ds = (DataSource)lookup(dataSource);
con = ds.getConnection();
//test the connection with something
con.getCatalog();
} catch (NamingException ne) {
_log.error("Did not find datasource " + dataSource + ". " + ne.getMessage());
success = false;
} catch (SQLException sqle) {
_log.error("Error while testing connection of datasource " + dataSource + ". " + sqle.getMessage());
success = false;
} finally {
if (con != null) {
try {
con.close();
} catch (SQLException sqle) {
_log.error("Could not close tested connection of Datasource " + ds + ", exiting tool!");
System.exit(1);
return success;
private Object lookup(String name) throws NamingException {
//I also tried to set the properties - with the same result
/*String host = "ormi://127.0.0.1:23791/myConApp";
Hashtable rmi_env = new Hashtable();
rmi_env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
rmi_env.put(Context.PROVIDER_URL, host);
rmi_env.put(Context.SECURITY_PRINCIPAL,"name");
rmi_env.put(Context.SECURITY_CREDENTIALS,"password");
InitialContext ctxInitial = new InitialContext();
ctxInitial.list(""); //need this to check if there actually is a context
Object o = ctxInitial.lookup(name);
ctxInitial.close();
return o;
public static void main(String[] args) {
DataSourceChecker dsc = new DataSourceChecker(args); //The constructor simply processes the command line args
dsc.run();Hi,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Some JMS objects do not show up in JNDI tree
Hello friends. I have a situation where some of my JMS Queues do not show up in
the JNDI tree. Other Queues / Topics show up fine. I cannot find any difference
in the interface that tells me what my cause this to happen. Any insight would
be appreciated.
brianare you using a cluster? if so check the multicast to see if its working
right.
Where are you looking up the JNDI tree? in the console or are you checking
the JNDI tree via weblogic.Admin LIST command? the LIST command may be a
better way to see it for sure.
sree
"Brian" <[email protected]> wrote in message
news:40b74519$1@mktnews1...
>
Hello friends. I have a situation where some of my JMS Queues do not showup in
the JNDI tree. Other Queues / Topics show up fine. I cannot find anydifference
in the interface that tells me what my cause this to happen. Any insightwould
be appreciated.
brian
Maybe you are looking for
-
SOFM: Dsiplay method is not working when called from ABAP Webdynpro
Hi All, I want to open an attachment from ABAP Webdynpro. I have approached in this fashion: 1) Get the attachments as SOFM object key 2) On Click of a link on Webdynpro, I am calling a function module within which I am creating an instance of the SO
-
Issue: 1) How can Can we simply generate a PDF and Email/Fax/Print via SAP Connect. 2)If so can we archive to OnDemand? Or can we recreate a image in SAP (similar to MR90 for Self Bills) I am not sure how to achive it and also whether it is possible
-
Everytime i try to download a file that i've purchesed i get a currupted file prompt? ***?
So once upon a time I bought a song, then while it was downloading it continued to download,over and over again about 5 times, each time getting to the desired amount of MB to be completed only to restart again....then i get this error prompt saying
-
Problème export PDF depuis Indesign CS6
Salut, j'ai un souci avec indesign CS6. il m'arrive de récupérer de vieux pdf d'Xpress (bouhhhhh) et de devoir les importer dans indesign. jusque la tout va bien. A l'exportation en PDF, inDesign plante systématiquement. Par contre, SI je n'ai pas un
-
RME 4.1 Software distribution gives generic error
Using LMS 3.0.1 with RME 4.1.1 I get an error when trying to distribute images. It's same whether I used "By device" or "by image".The recommendation are run for 90 seconds and then the result are always "failure".I've tried different devices&images.