Can a single JNDI tree be shared by multiple, non-clustered servers?

We have a situation involving multiple, but non-clustered, WebLogic servers,
say Server 1 and Server 2. A client needs to access an EJB which happens to
be located only on Server 2. We would prefer that the client not need to
know the exact location of the EJB, but use the naming service hosted by a
designated server (Server 1) to locate the EJB.
At a minimum, this would require that both servers bind their respective
EJB's into a common, shared JNDI naming tree hosted by Server 1.
Is this possible?
John Armstrong
WebLink Wireless, Inc.
[email protected]

hi,
I have not tried this, althoug with the webogic rmi and weblogic jndi
implementation I would guess this is straightforward.
Binding remote objects in WL JNDI binds the stubs only, not the object
itself. The worst case scenario here would be for you to implement proxies
and bind them in JNDI, although I would guess that binding the home object
should give you the required functionality.
Just try it, rebind the home object on a different server than the one the
bean is deployed on and test. My guess is that it will work.
(I repeat : I have not tested this my self, this is just a suggestion)
Regards,
Anders M.
John N. Armstrong <[email protected]> skrev i
meldingsnyheter:3a93faba$[email protected]..
We have a situation involving multiple, but non-clustered, WebLogicservers,
say Server 1 and Server 2. A client needs to access an EJB which happensto
be located only on Server 2. We would prefer that the client not need to
know the exact location of the EJB, but use the naming service hosted by a
designated server (Server 1) to locate the EJB.
At a minimum, this would require that both servers bind their respective
EJB's into a common, shared JNDI naming tree hosted by Server 1.
Is this possible?
John Armstrong
WebLink Wireless, Inc.
[email protected]

Similar Messages

  • Can a single Firefox profile be shared between multiple machines?

    I work in a library where we have multiple desktops that are managed by PC Reservation software and equipped with Deep-Freeze. Rather than have to go from one machine to another every time we want to update bookmarks or settings we would like to have a common profile installed on our local server that all of the machines can refer to. We are not interested in any Cloud based options and would prefer to maintain everything locally. This administration has to be local and we absolutely will not be using a Cloud based option like Sync, XMarks or Delicious. We will simply stop using Firefox in the library altogether before we would resort to one of those options.

    hi,
    I have not tried this, althoug with the webogic rmi and weblogic jndi
    implementation I would guess this is straightforward.
    Binding remote objects in WL JNDI binds the stubs only, not the object
    itself. The worst case scenario here would be for you to implement proxies
    and bind them in JNDI, although I would guess that binding the home object
    should give you the required functionality.
    Just try it, rebind the home object on a different server than the one the
    bean is deployed on and test. My guess is that it will work.
    (I repeat : I have not tested this my self, this is just a suggestion)
    Regards,
    Anders M.
    John N. Armstrong <[email protected]> skrev i
    meldingsnyheter:3a93faba$[email protected]..
    We have a situation involving multiple, but non-clustered, WebLogicservers,
    say Server 1 and Server 2. A client needs to access an EJB which happensto
    be located only on Server 2. We would prefer that the client not need to
    know the exact location of the EJB, but use the naming service hosted by a
    designated server (Server 1) to locate the EJB.
    At a minimum, this would require that both servers bind their respective
    EJB's into a common, shared JNDI naming tree hosted by Server 1.
    Is this possible?
    John Armstrong
    WebLink Wireless, Inc.
    [email protected]

  • Multiple WLS 4.5.1 processes using 1 single JNDI tree

    Currently we are using 1 WLS process to deploy different beans in
    our project. We know that all the deployed beans will be registered
    within the JNDI service running in the context of this process.
    But now we would like to change this configuration. We would like to
    run more than 1 WLS processes deloying all different beans
    which are using the same JNDI tree.
    Example:
    Process 1 delopys BEAN_A, BEAN_B ----> uses ------------
    Process 2 delopys BEAN_C, BEAN_D --------------> JNDI Service Process
    Process 3 delopys BEAN_E, BEAN_F ----> uses ------------
    How can we do this?
    Thanks
    Christoph

    If your WLS4.5.1 and WLS5.1 use different IP address, they can use the same
    port. If they use the same IP address, they can not use the same port
    number.
    Cheers - Wei
    Mark Ulmer <[email protected]> wrote in message
    news:8gj41s$md5$[email protected]..
    I understand that multiple instances of the WLS can be run on the samebox,
    they are just listening on different ports. Does this still hold true ifI
    am using a product that runs on top of WLS 4.5.1 and would like to have my
    own WLS 5.1 instance running on the same box? Can this be done if I keep
    the classpaths and weblogic_classpaths and all other related environment
    settings seperate?
    Thanks,
    Mark Ulmer

  • Can an iPhoto library be used/shared on multiple macs?

    I have a MacBook Pro and a MacMini and I want both to have the same iPhoto library so I do not have to identify faces and geo-tag the same pictures again.  Is this possible?

    There is a way.  If the two Macs are on a wired LAN the library can be placed on an external HD connected to one of the Mac so both can access the same library, but not a the same time.  The EHD should be formatted as follows:
    It is not advisable to access the library wirelessly as dropouts do occur and if one does while editing a photo or writhing to the library's database file the library can be damaged.  The likelihood of that is high.
    OT

  • Can one installation of SSIS be shared by multiple instances on the same physical box?

    Hello everyone, 
    I hope I'm posting this question on the correct forum. 
    We are short on money this year and we decided to purchase one physical system to represent Development and QA. 
    I am designing an architecture around my systems where I would have a two SQL Server Instances (2014, Enterprise Ed), one for each environment: 
    DVSV-ODS01\DEV
    DVSV-ODS01\QA
    The only possible problem is SSIS, which I cannot have multiple installations of SSIS on the same box.
    Is it possible to have the SSIS service serving the two SQL Server instances installed on the same physical box?
    Thanks for your help. 

    Not on the same physical box, but you can go with running say the QA environment on a Virtual Machine.
    E.g. the very free VirtualBox should do it. And then you can install two SSIS instances.
    You can even access them simultaneously this way.
    Arthur
    MyBlog
    Twitter

  • Shared JNDI Tree WL 10 and SAP Web AS

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

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

  • Jndi tree

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

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

  • The server deploy EJB but I run EJB Client program,The error msg is can't find JNDI

    Hi all:
    I am using Weblogic 6.1/SP2. I use the console to start
    server and deploy EJB jar,from the msg I see my EJB jar
    been deployed. When I run EJB Client program, the error
    msg is can't find JNDI name t3://URL:11003.....
    I check my ejb-jar.xml amd weblogic-ejb-jar.xml are fine.
    Last week I did deploy EJB and ran the client both
    suceessful. Any ideas, Thank you.

    Sabha:
    Thank you for your help info, I soloved the problem.
    The problem is the ejb jar was deleted(I don't why)
    then System Admin to deploy EJB jar from Admin console.
    After that everything is fine.
    "Sabha" <[email protected]> wrote:
    Run weblogic.Admin -url ... LIST to see whether the JNDI name is there
    . or
    you can view the jndi tree of the server from the console (right click
    on
    server name) and check whether the ejb home is bound to the correct jndi
    name.
    -Sabha
    "Matthew Shinn" <[email protected]> wrote in message
    news:[email protected]..
    Hi Albert,
    I would double check to make sure the EJB was indeed deployed (check
    server log). What message did you see that leads you to believe itwas
    successfully deployed? Also, verify the JNDI name you are lookingup in
    your client matches the JNDI name for the EJB. If this doesn't solve
    the problem, please post the error message and stack trace you are
    seeing on the client.
    - Matt
    Albert Pi wrote:
    Hi all:
    I am using Weblogic 6.1/SP2. I use the console to start
    server and deploy EJB jar,from the msg I see my EJB jar
    been deployed. When I run EJB Client program, the error
    msg is can't find JNDI name t3://URL:11003.....
    I check my ejb-jar.xml amd weblogic-ejb-jar.xml are fine.
    Last week I did deploy EJB and ran the client both
    suceessful. Any ideas, Thank you.

  • How to access JNDI tree of Admin Server from Managed Server

    Hello,
    I created Managed and Admin Server for Domain.
    On Managed Server I use:
    InitialContext con = new InitialContext()
    It points to Managed Server local JNDI tree and
    Managed Server can't find JNDI tree of Admin Server.
    Looks like Managed Server is regular remote client of Admin Server.
    How to access JNDI tree of Admin Server from Managed Server?
    Thanks.
    Oleg.

    Hello,
    I created Managed and Admin Server for Domain.
    On Managed Server I use:
    InitialContext con = new InitialContext()
    It points to Managed Server local JNDI tree and
    Managed Server can't find JNDI tree of Admin Server.
    Looks like Managed Server is regular remote client of Admin Server.
    How to access JNDI tree of Admin Server from Managed Server?
    Thanks.
    Oleg.

  • Distinction of EJBs in shared clusterwide JNDI-Tree

    Hi,
              for logging issues i want to browse the shared clusterwide JNDI-Tree. As far
              as i know, the clusterwide JNDI-Tree contains all services of any deployed
              EJB in the cluster.
              My problem is that i want do distinguish between the EJBs on the unique
              Application Servers in the cluster. I need to get information about the
              ApplicationServer/Thread the EJB is running in.
              -Is it possible to get this information out of the clusterwide JNDI-Tree of
              WLS6.0sp1?
              -Is there a way to work with the replica-aware stubs of clusterable EJBs to
              distinguish between "originals" and their replicas on other AppServers?
              -Which type of EJBs can be accessed? All types?
              -How can this task be achieved?
              Thanks in advance for your help
              René
              

    "René Eßer" wrote:
              > Hi,
              >
              > for logging issues i want to browse the shared clusterwide JNDI-Tree. As far
              > as i know, the clusterwide JNDI-Tree contains all services of any deployed
              > EJB in the cluster.
              Yes, the cluster wide JNDI tree contains everything that is deployed in the
              cluster.
              > My problem is that i want do distinguish between the EJBs on the unique
              > Application Servers in the cluster. I need to get information about the
              > ApplicationServer/Thread the EJB is running in.
              I don't understand what you mean here. "EJB's on the unique App Servers in the
              cluster". To find out which thread is running you can do a
              Thread.currentThread().getName()
              >
              > -Is it possible to get this information out of the clusterwide JNDI-Tree of
              > WLS6.0sp1?
              No not really.
              >
              > -Is there a way to work with the replica-aware stubs of clusterable EJBs to
              > distinguish between "originals" and their replicas on other AppServers?
              This is all hidden and transperent to the users.
              -- Prasad
              >
              > -Which type of EJBs can be accessed? All types?
              >
              > -How can this task be achieved?
              >
              > Thanks in advance for your help
              >
              > René
              

  • I'm trying to share folder between users on a single mac.  I put the folder in "shared," set permissions so other user can read and write, enabled file sharing, but can't find the folder on the second user's account.  Any help?

    I'm trying to share a folder between users on a single mac.  I want both users to be able to read and write so the folder stays current on both accounts.  I put the folder in "shared," set permissions on folder so other user can read and write, enabled file sharing, but can't find the folder on the second user's account.  Any help?

    Did you log out of one account and into the other or just used Fast user switching?
    Is the permissions set to anyone?
    When you move data to teh Shared folder is it copied or just moved?
    If copied then it's not a folder both can access, just a way station like a USB thumb drive that things are coped too and off of likely.
    You can run this #5 on each user account to reset the user permissions once they are taken back out of the Shared folder
    Step by Step to fix your Mac

  • Can a single PDF file url be shared on facebook or website?

    Can a single PDF file url be shared on facebook or website?

    Hi sday706,
    Sure thing! If you share your file via Acrobat.com or Adobe Send, you can generate a URL for that file by choosing Create Anonymous Link after you've selected the file that you want to share.
    Best,
    Sara

  • 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

  • Error While Viewing JNDI Tree

              Hi
              I'm facing the following problem while viewing the JNDI tree. I had configured
              two servers ejbServer,ejbServer1 both clustered, i can able to start both the
              servers, but in the JNDI tree when i click ejbServer or Replication Manager
              i'm getting the following error please help me out.
              An unexpected error was encountered in processing your request.
              Exception
              javax.naming.NameNotFoundException: Unable to resolve weblogic.transaction.coordinators.ejbServer.
              Resolved: 'weblogic.transaction.coordinators' Unresolved:'ejbServer' ; remaining
              name ''
                   <>
              Current Date
              Mon Aug 27 09:15:19 GMT+08:00 2001
              Console Release Build
              6.0 Service Pack 2
              Console Build
              6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              Server Release Build
              6.0 Service Pack 2
              Server Build
              6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              All Server Product Versions
              WebLogic Server Build:     6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              WebLogic XML Module:     6.0 Service Pack 2 05/24/2001 12:34:27 #117037
              Request Info
              Protocol: HTTP/1.1
              ServerName: 127.0.0.1
              ServerPort: 7001
              Secure: false
              ContextPath: /console
              ServletPath: /common/error.jsp
              QueryString: null
              PathInfo: null
              PathTranslated: null
              RequestURI: /console/common/error.jsp
              AuthType: Basic
              ContentType: null
              CharacterEncoding: null
              Locale: hi
              Method: GET
              Session: weblogic.servlet.internal.session.MemorySessionData@37b6ef
              RequestedSessionId: O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q/console
              RequestedSessionIdFromCookie: true
              RequestedSessionIdFromURL: false
              UserPrincipal: system
              RemoteUser: system
              RemoteAddr: 127.0.0.1
              RemoteHost: localhost
              Parameters
              binding = ejbServer
              context = weblogic.transaction.coordinators
              Attributes
              console.original./console/common/error.jsp.ContextPath = /console
              console.original./console/common/error.jsp.Method = GET
              console.original./console/common/error.jsp.RemoteUser = system
              console.original./console/common/error.jsp.RequestURI = /console/common/error.jsp
              console.original./console/common/error.jsp.ServletPath = /common/error.jsp
              console.original./console/panels/mbean/JNDIBinding.jsp.ContextPath = /console
              console.original./console/panels/mbean/JNDIBinding.jsp.Method = GET
              console.original./console/panels/mbean/JNDIBinding.jsp.QueryString = context=weblogic.transaction.coordinators&binding=ejbServer
              console.original./console/panels/mbean/JNDIBinding.jsp.RemoteUser = system
              console.original./console/panels/mbean/JNDIBinding.jsp.RequestURI = /console/panels/mbean/JNDIBinding.jsp
              console.original./console/panels/mbean/JNDIBinding.jsp.ServletPath = /panels/mbean/JNDIBinding.jsp
              console.preferences.ContextKey = /panels/mbean/JNDIBinding.jsp
              javax.servlet.include.context_path = /console
              javax.servlet.include.request_uri = /console/common/requestinfo.jsp
              javax.servlet.include.servlet_path = /common/requestinfo.jsp
              javax.servlet.jsp.jspException = javax.naming.NameNotFoundException:
              Unable to resolve weblogic.transaction.coordinators.ejbServer. Resolved: 'weblogic.transaction.coordinators'
              Unresolved:'ejbServer' ; remaining name ''
              weblogic.httpd.user = system
              weblogic.management.console.tags.ContentTag = java.lang.Object@397a54
              weblogic.management.console.tags.HeaderTag = java.lang.Object@e4a33
              Headers
              Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel,
              application/msword, application/vnd.ms-powerpoint, */*
              Accept-Encoding = gzip, deflate
              Accept-Language = hi
              Authorization = Basic c3lzdGVtOm1hbmFnZXIx
              Connection = Keep-Alive
              Cookie = JSESSIONID=O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q!2557472653882942880!-1062729946!7001!7002
              Host = 127.0.0.1:7001
              User-Agent = Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
              BrowserInfo
              User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
              IE: true
              Netscape: false
              Supported: true
              JavscriptHrefs: false
              TableCellClick: true
              DocumentReloadedOnResize: false
              DropdownStretchable: true
              CellSpacingBlank: false
              EmptyCellBlank: false
              ImgOnclickSupported: true
              TableBorderFancy: true
              PartialToWideTables: false
              Server System Properties
              awt.toolkit = sun.awt.windows.WToolkit
              bea.home = d:\Weblogic
              cloudscape.system.home = ./samples/eval/cloudscape/data
              file.encoding = Cp1252
              file.encoding.pkg = sun.io
              file.separator = \
              java.awt.fonts =
              java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
              java.awt.printerjob = sun.awt.windows.WPrinterJob
              java.class.path = .;d:\Weblogic\jdk130\lib\tools.jar;d:\Weblogic\wlserver\lib\weblogic_sp.jar;d:\Weblogic\wlserver\lib\weblogic.jar;d:\Weblogic\wlserver\lib\xmlx.jar;d:\Weblogic\wlserver\lib\ejb20.jar;d:\Weblogic\wlserver\samples\eval\cloudscape\lib\cloudscape.jar;;;;d:\Weblogic;d:\Weblogic\wlserver\bin\oci816_8;d:\Oracle_Home\iSuites\jdbc\lib\classes12.zip;d:\Weblogic\wlserver\lib;d:\Oracle_Home\iSuites\lib\xmlparserv2.jar;d:\JDeveloper\lib\xsu12.jar;;
              java.class.version = 47.0
              java.ext.dirs = d:\Weblogic\jdk130\jre\lib\ext
              java.home = d:\Weblogic\jdk130\jre
              java.io.tmpdir = C:\TEMP\
              java.library.path = d:\Weblogic\jdk130\bin;.;C:\WINNT\System32;C:\WINNT;.\bin;D:\Oracle_Home\iSuites\BIN;D:\Oracle_Home\iSuites\Apache\Perl\5.00503\bin\mswin32-x86;C:\Program
              Files\Oracle\jre\1.1.7\bin;C:\WINNT\system32;C:\WINNT;C:\VisualCafeSE\Java2\Bin;C:\Program
              Files\Common Files\WebGain Shared;C:\VisualCafeSE\Bin;
              java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
              java.naming.factory.url.pkgs = weblogic.jndi.factories
              java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|weblogic.net|weblogic.utils
              java.runtime.name = Java(TM) 2 Runtime Environment, Standard
              Edition
              java.runtime.version = 1.3.0-C
              java.security.policy = =d:\Weblogic\wlserver/lib/weblogic.policy
              java.specification.name = Java Platform API Specification
              java.specification.vendor = Sun Microsystems Inc.
              java.specification.version = 1.3
              java.vendor = Sun Microsystems Inc.
              java.vendor.url = http://java.sun.com/
              java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
              java.version = 1.3.0
              java.vm.info = mixed mode
              java.vm.name = Java HotSpot(TM) Client VM
              java.vm.specification.name = Java Virtual Machine Specification
              java.vm.specification.vendor = Sun Microsystems Inc.
              java.vm.specification.version = 1.0
              java.vm.vendor = Sun Microsystems Inc.
              java.vm.version = 1.3.0-C
              javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
              javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
              javax.xml.parsers.DocumentBuilderFactory = weblogic.xml.jaxp.RegistryDocumentBuilderFactory
              javax.xml.parsers.SAXParserFactory = weblogic.xml.jaxp.RegistrySAXParserFactory
              jmx.implementation.name = JMX RI
              jmx.implementation.vendor = Sun Microsystems
              jmx.implementation.version = 1.0
              jmx.specification.name = Java Management Extensions
              jmx.specification.vendor = Sun Microsystems
              jmx.specification.version = 1.0 Final Release
              line.separator =
              os.arch = x86
              os.name = Windows NT
              os.version = 4.0
              path.separator = ;
              sun.boot.class.path = d:\Weblogic\jdk130\jre\lib\rt.jar;d:\Weblogic\jdk130\jre\lib\i18n.jar;d:\Weblogic\jdk130\jre\lib\sunrsasign.jar;d:\Weblogic\jdk130\jre\classes
              sun.boot.library.path = d:\Weblogic\jdk130\jre\bin
              sun.cpu.endian = little
              sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx
              pentium i486 i386
              sun.io.unicode.encoding = UnicodeLittle
              user.dir = D:\Weblogic\wlserver
              user.home = C:\WINNT\Profiles\venkata
              user.language = en
              user.name = venkata
              user.region = US
              user.timezone = Asia/Singapore
              weblogic.Domain = DNSdomain
              weblogic.Name = DNSserver
              weblogic.management.discover = true
              weblogic.security.jaas.Configuration = weblogic.security.internal.ServerConfig
              weblogic.security.jaas.Policy = d:/Weblogic/wlserver/lib/Server.policy
              

    [att1.html]
              

  • MBeanServer location in JNDI tree

    Hello,
    I'm testing methods that use a MBeanServer from JConsole and MBean browser in EM console. I launch the JConsole using this parameters:
    jconsole -J-Djava.class.path=/home/user/wlfullclient-10.3.5.0.jar:/usr/java/jdk1.6.0_30/lib/jconsole.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
    When I use the JConsole for testing I obtain the MBeanServer in this way:
    InitialContext ctx = new InitialContext();
    server = (MBeanServer)ctx.lookup("java:comp/jmx/runtime");
    And when I use the MBean browser I have to to use this code:
    server = (MBeanServer)ctx.lookup("java:comp/env/jmx/runtime");
    I'm following the next Oracle documentation, but I want to know if there is other way to use only once String to found the MBeanServer in the JNDI tree.
    Does anybody know a different way to do this?
    Thanks in advance,
    Make Local Connections to the Runtime MBean Server+
    Local clients can access a WebLogic Server instance’s Runtime MBean Server through the JNDI tree instead of constructing a JMXServiceURL object. Only the Runtime MBean Server registers itself in the JNDI tree.+
    When accessed from JNDI, the Runtime MBean Server returns its javax.management.MBeanServer interface. This interface contains all of the methods in the MBeanServerConnection interface plus additional methods such as registerMBean(), which local process can use to register custom MBeans. (See MBeanServer in the J2SE 5.0 API Specification.)+
    If the classes for the JMX client are located at the top level of an enterprise application (that is, if they are deployed from the application’s APP-INF directory), then the JNDI name for the Runtime MBean Server is:+
    java:comp/jmx/runtime
    If the classes for the JMX client are located in a Java EE module, such as an EJB or Web application, then the JNDI name for the Runtime MBeanServer is:+
    java:comp/env/jmx/runtime
    For example:
    InitialContext ctx = new InitialContext();
    server = (MBeanServer)ctx.lookup("java:comp/env/jmx/runtime");

    Hi,
    I have same problem.
    I have developed some libs (with common functionality to be used in many places, utils, and so) which I deploy in $DOMAIN/lib. I also have an ear, with ApplicationLifecycleListener to register some MBeans in the MBeanServer and they make use of this shared libs.
    The thing is that if I access on of my MBeans from JConsole and if I access the same MBean from within em console, my app needs to look at different locations in the JNDI tree for the MBeanServer. Shouldn't this code, as it is running in the same location need to locate the MBeanServer the same way? Or because the client application in one case is remote, and in the other is local, need to look for the MBeanServer in one location and if not found in the other.
    Think that code is deployed as a Util class in the DOMAIN/lib directory.
    Thanks,

Maybe you are looking for