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.

Similar Messages

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

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>

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 list

Hi 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

Conflict start: You tried to bind an object under the name abc.Scheduler

I have deployed my application on the WLS which is configured for clustred with 2 managed server and one admin server in the same machine. I see the below error on both of the managedServer consoles. can any one please help me resolving this issue.
<Conflict start: You tried to bind an object under the name abc.Scheduler in the JNDI tree. The object from -2433108061996587758S:192.168.0.61:[7014,7014,-1,-1,-1,-1,-1]:SingleDomainClusterTake2:ManagedServer1 is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.>
Regards
Suresh.

Hi Jay,
Below is the code snippet where I am binding the Schedular Object to a JNDI abc.Schedular and I got the above error message when I trying to deploy the application in clustered environment.
Code Snippet where binding the Schedular Object
private static final String JNDI_NAME = "abc/Scheduler";
Hashtable ht=new Hashtable ();
InitialContext context = new InitialContext();
scheduler = new Scheduler();
scheduler.setStorage(new DatabaseSchedulerStorage());
context.bind(JNDI_NAME, scheduler);
Code Snippet for looking up the schedular object
protected Scheduler getScheduler() throws NamingException {
if (scheduler != null) {
return scheduler;
Scheduler s=null;
if(workaround){
s=((ThreadManager)SchedulingServlet.getThreadManager()).getScheduler();
}else{
InitialContext context = new InitialContext();
s = (Scheduler) context.lookup("reactor/Scheduler");
if (s.getStorage() == null) {
s.setStorage(new DatabaseSchedulerStorage());
scheduler=s;
return scheduler;
I have added "ht.put(WLContext.REPLICATE_BINDINGS, "false");" to get rid of the conflict error but I what this object to be clustrable and you please let me know how do I make this object clustrable.
I am using quartz schedular.
Regards
Suresh.

30EA1 /2.*: Double-clicking objects in the navigator tree

Hi,
There is an inconsistency in double-clicking objects in the navigator tree:
When Preferences - Database - ObjectViewer - Open Objects on Single Click is checked, double-clicking e.g. a table in the navigator will still open it the same way as single-clicking it.
However, when Preferences - Database - ObjectViewer - Open Objects on Single Click is not checked, double-clicking the table in the navigator will open it, and expand the columns. The latter is quite irritating, especially on large tables.
Can this be bugged, so double-clicking the table in the navigator will just open it?
Thanks,
K.

The node is expanded on double click irrespective of what the preferenceIs this a typo or does it really expand always for you? For me it only expands with "single click objects" disabled.
windows explorer also does the sameYes, and I'd even say that's the desired behaviour, especially since it's the only action taken.
Common sense and standards are against taking 2 different actions at the same time. One should override the other.
Ideally, double click with "single click objects" disabled would just open the object, and double click with "single click objects" enabled could expand the node as in the Windows Explorer (but doesn't have to).
So that's almost completely the other way around as we get it now.
Thanks,
K.

Could not lookup PortalManagerHome in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager

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 Hans

Neeraj -
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.

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,
Mario

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.

Binding custom objects in weblogic JNDI

I noticed that if I bind a custom object, the object is not available after the weblogic
restart. Is there anyway to bind an object permanently in the weblogic JNDI..

In article <[email protected]>, [email protected] says...
Murali <[email protected]> wrote:
I noticed that if I bind a custom object, the object is not available after the weblogic
restart. Is there anyway to bind an object permanently in the weblogic JNDI..No.
Perhaps what your trying to accomplish could be handled via a startup
class that did the bind for you.
Bob

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.

Value binding an object to the request scope

Hello,
In one page I have the results conducted from doing a search. Each row displayed in that page represents a user, and there is a link within each row that will facilitate the editing of that user in another page.
Here is the code for the link in the "results" page:
<h:column>
     <h:commandLink id="editLink" action="#{pc_Search_user_results.editUser}">
          <h:outputText value="Edit" />
          <f:param name="userId" value="#{user.id}" />
     </h:commandLink>
</h:column>My second page (that is, the one that will allow edits to be made) expects a "User" instance to be available as part of the request:
<managed-bean>
<managed-bean-name>pc_EditUser</managed-bean-name>
<managed-bean-class>pagecode.jsp.EditUser</managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
     <managed-property>
          <description>
                    Should be an instance of the user that was selected from
                    the search results page.
          </description>
          <property-name>user</property-name>
          <value>#{requestScope.user}</value>
     </managed-property>
</managed-bean>I have that variable defined in the EditUser backing bean for the "edit" page with the appropriate getter/setter. The problem is that instead of getting a "User" instance in the bean, I'm getting a null value for it instead. I'm trying to set the instance in the method associated with the command link in my "results" page. That is, in my SearchUserResults bean, which is the backing bean for my "results" page, I have the following code:
public String editUser() {
        HtmlCommandLink link = this.getCommandLinkById("editLink");
        String id = null;
        Map map = link.getAttributes();
        List children = link.getChildren();
        for (int i = 0; i < children.size(); i++) {
            if (children.get(i) instanceof UIParameter) {
                UIParameter parm = (UIParameter) children.get(i);
                id = (String) parm.getValue();
                break;
        User user = null;
        Iterator iterator = this.users.iterator();
        while (iterator.hasNext()) {
            user = (User) iterator.next();
            if (id.equals(user.getId())) {
                break;
        facesContext.getApplication()
                    .createValueBinding("#{requestScope.user}").setValue(
                        facesContext, user);
        return "success";
    }All I want to get in my backing bean for the "edit" page is a valid "User" instance, which should be set when a new instance of EditUser is created per request. Obviously, I'm not understanding what is happening for this simple scenario. Please chime in with suggestions or explanations! Thanks.
Jeff

Frank,
Thanks for your reply.
Yes. I have dragged the collection called "GetYearsDataRequest" (which has 2 attributes) to the view as to create new form with submit button. Then i dragged the method on the button to bind the method called "GetYears".
But actually the method GetYears is required complex type "GetYearsDataRequest" as input. I see the collection and the object/complex types are seperated form visual perspective.
I tried dragging method to create parameter form, but unfortunately it created GetYearsDataRequest as text field rather I would like to see its attribute in the form.
I am not sure how to bind the attributes to the input object/complex type (GetYearsDataRequest). I think I am missing this step. Pls help me on this.
I hope I answered to your question.
Please let me know if you need more info.l
Thanks!
Rajasekar.

Binding huge object to the jndi tree.

Similar Messages

Maybe you are looking for