JNDI replication in cluster

Is there a way to force the JNDI replication?

It is on by default, unless you specifically disabled it:
 http://e-docs.bea.com/wls/docs61/javadocs/weblogic/jndi/WLContext.html
 REPLICATE_BINDINGS
 public static final java.lang.String REPLICATE_BINDINGS
 Cluster-specific: Specifies whether tree modifications are replicated
 and is only applicable when connecting to WebLogic Servers that are running
 in a cluster. By default, any modification to the naming tree is replicated
 across the cluster, which ensures that any server can act as a naming server
 for the entire cluster. Setting this property to false changes this behavior
 and should be done with extreme caution: a false setting means that modifications
 to the tree caused by bind, unbind, createSubcontext, and destroySubcontext
 will not be replicated.
 Understand the implications of this property before changing its default (true).
 Pothiraj <[email protected]> wrote:
 > Is there a way to force the JNDI replication?
 Dimitri

Similar Messages

JNDI replication within a cluster

Hi to all of you,
we successfully enabled HTTP Session replication and tested the failover. We would also like to setup a JNDI replication, so that we can use it as a storage for some shared data -- as stated in http://download.oracle.com/docs/cd/B10464_05/web.904/b10324/cluster.htm this should be enabled automatically, once EJB replication is enabled.
With some problems we finally enabled EJB replication (we configured it through orion-application.xml) and the required replication policy is propagated to our statful beans. Anyway, the JNDI is still not replicated over the machines.
We are running latest OAS 10g, cluster is MultiCast on RedHat Enterprise, replication policy for Stateful beans is set to 'onRequestEnd' (we tried all the options :), our application is normal ear with 1 ejb and 1 war archive and apart from JNDI replication, it works as expected.
Is there some trick that is not mentioned or that we may overlooked in documentation to enable JNDI replication?
Kind Regards,
Martin

Hopefully solved -- though the documentation explicitly mentions rebinding as not working, after any changes made to value stored in JNDI context you should just re-bind the value to the JNDI context; the value is replicated to other JNDI contexts.
m.

Cluster-wide JNDI replication

I have a question about cluster wide JNDI replication. I am on weblogic
 7.0 sp2, solaris 8. I have 2 weblogic servers in a cluster and two
 asynchronous JVM's connect to this cluster. The two weblogic servers
 would be w1 and w2 and the JVMs would be j1
 w1 creates a stateful ejb. The handle to this ejb is put on the JNDI
 tree. A JMS message is created which contains the key to the handle
 object. A JMS message is sent which is picked up by one of the JVM's say
 j1. j1 tries to do a lookup of the handle using the key in the JMS
 message and it is not able to find the handle object.
 The reason is that j1 is trying to connect to the w2 to find the handle.
 The change to the jndi tree is not propagated to w2 yet and hence the
 error. Any ideas on why it would take so long to communicate the jndi
 tree? My jndi tree has hardly anything in it. There are a couple of JMS
 connection factories and 3 ejbs and couple of JMS queues.
 Would appreciate any kind of help. I am going to migrate storing the ejb
 handles to another persistent store instead of the jndi tree but till
 then any insight into this problem would be helpful.
 Please don't advice solutions like using Thread.sleep and trying again
 Thanks,
 Shiva.


Shiva,
 > I have a question about cluster wide JNDI replication. I am on weblogic
 > 7.0 sp2, solaris 8. I have 2 weblogic servers in a cluster and two
 > asynchronous JVM's connect to this cluster. The two weblogic servers
 > would be w1 and w2 and the JVMs would be j1
 >
 > w1 creates a stateful ejb. The handle to this ejb is put on the JNDI
 > tree. A JMS message is created which contains the key to the handle
 > object. A JMS message is sent which is picked up by one of the JVM's say
 > j1. j1 tries to do a lookup of the handle using the key in the JMS
 > message and it is not able to find the handle object.
 >
 > The reason is that j1 is trying to connect to the w2 to find the handle.
 > The change to the jndi tree is not propagated to w2 yet and hence the
 > error. Any ideas on why it would take so long to communicate the jndi
 > tree? My jndi tree has hardly anything in it. There are a couple of JMS
 > connection factories and 3 ejbs and couple of JMS queues.
 That's an interesting problem. The handle should have enough information
 to locate the EJB. Are you explicitly trying to connect to W2 from J1 or
 something? That part didn't make sense to me.
 (While it's a different approach, if you need to share data real-time in a
 cluster, use our Coherence Java clustered cache software.)
 Peace,
 Cameron Purdy
 Tangosol, Inc.
 http://www.tangosol.com/coherence.jsp
 Tangosol Coherence: Clustered Replicated Cache for Weblogic
 "Shiva P" <[email protected]> wrote in message
 news:[email protected]...
 >

JNDI replication\lookup problems

 Hi,
 We have a WL5.1 SP12 cluster that until today consisted of 2 Solaris boxes running
 8 WL instances on the 2.6 OS.
 Today we attempted to add a third Solaris box, running 2 SP12 WL instances on the
 2.8 OS. These two new instances were identical to the other 8 in all respects apart
 from one ejb jar which they did not deploy (because of Solaris 2.8\JNI\JDK1.3.1 incompatiblilities).
 We figured that these new JVM could lookup this bean via the clustered JNDI and execute
 on one of the original 8 JVMs, so we did not deploy on these new servers. This worked
 fine on test (a 3 way cluster, on one box running Solaris 2.8 and SP10).
 However when we cut the new box in this morning we got javax.naming.NameNotFoundExceptions
 from the new JVMs.
 These new JVMs apeared to start fine, and everything looked as it should on the console,
 but still the error.
 so :
 what could it be :
 OS related - a clustering spanning 2.6 and 2.8 OSs
 SP 12 related ?
 Anybody encountered anything like this before ?
 Thanks in advance.
 Justin


 Yes, the EJB classes are in the server classpath.
 I assumed that JNDI replication occured as a resulting of enabling clustering.
 "Sabha" <[email protected]> wrote:
 >Are the ejb home/remote interfaces in the server classpath of the 2 newer
 >JVMs? Is jndi replication turned off?
 >
 >-Sabha
 >
 >"Justin" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Hi,
 >>
 >> We have a WL5.1 SP12 cluster that until today consisted of 2 Solaris boxes
 >running
 >> 8 WL instances on the 2.6 OS.
 >>
 >> Today we attempted to add a third Solaris box, running 2 SP12 WL instances
 >on the
 >> 2.8 OS. These two new instances were identical to the other 8 in all
 >respects apart
 >> from one ejb jar which they did not deploy (because of Solaris
 >2.8\JNI\JDK1.3.1 incompatiblilities).
 >> We figured that these new JVM could lookup this bean via the clustered
 >JNDI and execute
 >> on one of the original 8 JVMs, so we did not deploy on these new servers.
 >This worked
 >> fine on test (a 3 way cluster, on one box running Solaris 2.8 and SP10).
 >>
 >> However when we cut the new box in this morning we got
 >javax.naming.NameNotFoundExceptions
 >> from the new JVMs.
 >>
 >> These new JVMs apeared to start fine, and everything looked as it should
 >on the console,
 >> but still the error.
 >>
 >> so :
 >>
 >> what could it be :
 >>
 >> OS related - a clustering spanning 2.6 and 2.8 OSs
 >> SP 12 related ?
 >>
 >> Anybody encountered anything like this before ?
 >>
 >> Thanks in advance.
 >>
 >> Justin
 >>
 >>
 >>
 >
 >

What is "Replicate JNDI Name In Cluster" equivalent in Weblogic 10.3

Hi,
We are migrating one of our application from WL8 and WL10.3 where the existing setup using a non-distributed queue with "Replicate JNDI Name In Cluster" enabled. The cluster has 2 instances Ex: M1 and M2, both of these instances are using the aforesaid non-distributed queue which is tragetted only to M1 instance.
However the queue is targetted to M1, JNDI name associated to this Queue is available in M2 server so the MDB and Initial Context lookups are able to obtain the queue instance.
Now the issue is, we are unable to setup this feature in WL10.
1. We have created a UDQ and targetted to only M1.
2. MDBs and Intial context lookups from M2 is failing with NameNotFoundException.
Ultimatey the requirement is, the application deployed on cluster should consume/publish message only to/from queues available in M1. There is business reason behind this.
Please help.

Hi,
If your MDB is io version 3.0 then u can make use of the following Annotations to define the "*providerUrl*" of the server from where ur MDB wants to listen the messages.
Example: http://weblogic-wonders.com/weblogic/2010/06/09/mdb-with-non-container-specific-annotations/
initial-context-factory (Equivalent Property: initialContextFactory)
provider-url (Equivalent Property: providerURL)
ActivationConfigProperty(propertyName = “providerURL”, propertyValue = “your_MS1_Address”)
If you are using MDB2.0 then the same thing u need to do with "weblogic-ejb-jar.xml" file using <provider-url > Tag.
Thanks
Jay SenSharma

JNDI replication problems in WebLogic cluster.

I need to implement a replicable property in the cluster: each server could
update it and new value should be available for all cluster. I tried to bind
this property to JNDI and got several problems:
1) On each rebinding I got error messages:
<Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
to bind an object under the name example.TestName in the jndi tree. The
object you have bound java.util.Date from 10.1.8.114 is non clusterable and
you have tried to bind more than once from two or more servers. Such objects
can only deployed from one server.>
<Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
example.TestName for the object java.util.Date from 10.1.9.250 under the
bind name example.TestName in the jndi tree.>
As I understand this is a designed behavior for non-RMI objects. Am I
correct?
2) Replication is still done, but I got randomly results: I bind object to
server 1, get it from server 2 and they are not always the same even with
delay between operation in several seconds (tested with 0-10 sec.) and while
it lookup returns old version after 10 sec, second attempt without delay
could return correct result.
Any ideas how to ensure correct replication? I need lookup to return the
object I bound on different sever.
3) Even when lookup returns correct result, Admin Console in
Server->Monitoring-> JNDI Tree shows an error for bound object:
Exception
javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
Unresolved:'example' ; remaining name ''
My configuration: admin server + 3 managed servers in a cluster.
JNDI bind and lookup is done from stateless session bean. Session is
clusterable and deployed to all servers in cluster. Client invokes session
methods throw t3 protocol directly on servers.
Thank you for any help.

It is not a good idea to use JNDI to replicate application data. Did you consider
using JMS for this? Or JavaGroups (http://sourceforge.net/projects/javagroups/) -
there is an example of distibuted hashtable in examples.
Alex Rogozinsky <[email protected]> wrote:
I need to implement a replicable property in the cluster: each server could
update it and new value should be available for all cluster. I tried to bind
this property to JNDI and got several problems:
1) On each rebinding I got error messages:
<Nov 12, 2001 8:30:08 PM PST> <Error> <Cluster> <Conflict start: You tried
to bind an object under the name example.TestName in the jndi tree. The
object you have bound java.util.Date from 10.1.8.114 is non clusterable and
you have tried to bind more than once from two or more servers. Such objects
can only deployed from one server.>
<Nov 12, 2001 8:30:18 PM PST> <Error> <Cluster> <Conflict Resolved:
example.TestName for the object java.util.Date from 10.1.9.250 under the
bind name example.TestName in the jndi tree.>
As I understand this is a designed behavior for non-RMI objects. Am I
correct?
2) Replication is still done, but I got randomly results: I bind object to
server 1, get it from server 2 and they are not always the same even with
delay between operation in several seconds (tested with 0-10 sec.) and while
it lookup returns old version after 10 sec, second attempt without delay
could return correct result.
Any ideas how to ensure correct replication? I need lookup to return the
object I bound on different sever.
3) Even when lookup returns correct result, Admin Console in
Server->Monitoring-> JNDI Tree shows an error for bound object:
Exception
javax.naming.NameNotFoundException: Unable to resolve example. Resolved: ''
Unresolved:'example' ; remaining name ''
My configuration: admin server + 3 managed servers in a cluster.
JNDI bind and lookup is done from stateless session bean. Session is
clusterable and deployed to all servers in cluster. Client invokes session
methods throw t3 protocol directly on servers.
Thank you for any help.--
Dimitri

Clustered jndi replication

Does the replication in clustered jndi also support removing replicate
bindings
when you call unbind()?
When I programmatically bind a value (a String), it is replicated throughout
the cluster but when I try to unbind it only gets removed on one server.
Calling rebind with a new value doesn't work either; a message is printed to
the console saying there is a conflict. Has anyone seen this before and/or
is there
something I'm missing.
This is on weblogic5.1sp4.

This sounds like a bug.
I suggest that you file a bug report with our support organization. Be sure
to include a complete test case. They will also need information from
you -- please review our external support procedures:
http://www.beasys.com/support/index.html
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Jonathon Lee" <[email protected]> wrote in message
news:398b4219$[email protected]..
Does the replication in clustered jndi also support removing replicate
bindings
when you call unbind()?
When I programmatically bind a value (a String), it is replicatedthroughout
the cluster but when I try to unbind it only gets removed on one server.
Calling rebind with a new value doesn't work either; a message is printedto
the console saying there is a conflict. Has anyone seen this beforeand/or
is there
something I'm missing.
This is on weblogic5.1sp4.

JNDI in a cluster

Hi,
I've got a situation where I am deploying two different ears into two different Managed Servers in the same cluster. One ear is trying to look up an ejb from the other ear but for some reason the stateless bean iis not getting published into the JNDI tree of the cluster, and is only visible inside the managed server that the ear is deployed to. My question is: isn't the JNDI tree supposed to be global to all the servers inside of a cluster so registering an ejb in one will make it available to the rest of the cluster?

When you deploy ear file to one of the Managed server's part of cluste, the JNDI name can be seen only in that Managed server's tree, it cannot be seen in cluster JNDI tree or other managed servers JNDI tree.
- - Tarun

Flex session replication among cluster Help needed!

Hi,
I'am using Flex 3, LiceCycle Data Service 2.5.1, JBoss 4.2.1 in a web application. Our JBoss servers are in a cluster. We want to replicate Flex session among cluster, but it doesn't work. Did someone face issue with Flex session replication among application servers?
Thank you for your help
Gerard

Gerard, You will need to cluster the LCDS 2.5.1 instances the same way you clustered JBoss. Check out the "Configuring Data Services" chapter in the Admin guide: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/lcds/services_config_4.html -- Tom Jordahl Adobe <[email protected]> wrote > Hi, > > I'am using Flex 3, LiceCycle Data Service 2.5.1, JBoss 4.2.1 in a web > application. Our JBoss servers are in a cluster. We want to replicate Flex > session among cluster, but it doesn't work. Did someone face issue with > Flex session replication among application servers? > Thank you for your help > > Gerard

JNDI Exception on Cluster Redeployment

"Does anyone know what was the resolution on the attached newsgroup posting? i am experiencing a similar


 Jerry Davis <[email protected]> wrote:
 >"Does anyone know what was the resolution on the attached newsgroup posting?
 > i am experiencing a similar
 This seems to have gotten chopped. I am seeing the following error when attempting
 to hot-deploy (through the admin console) a simple stateless EJB
 to the second managed server, and receive this exception. The first managed server
 receives the deployment no problem; it's only the second managed
 server that throws the exception.
 <Jun 14, 2001 4:56:39 PM CDT> <Error> <J2EE> <Error deploying application HelloWorld_EJB:
 Could not deploy: 'HelloWorld_EJB.jar': JNDI name in use
 >
 <Jun 14, 2001 4:56:39 PM CDT> <Error> <Management> <InvocationTargetException
 setting attribute Deployed on MBean wwt:Name=HelloWorld_EJB,Location=testlogic2Server,Type=ApplicationConfig
 to value true. Method: public void weblogic.management.mbeans.custom.Application.setDeployed(boolean)
 throws weblogic.management.DeploymentException,weblogic.management.UndeploymentException
 weblogic.management.DeploymentException: Could not deploy: 'HelloWorld_EJB.jar':
 JNDI name in use
 at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
 at weblogic.j2ee.Application.deploy(Application.java:167)
 at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
 at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:217)
 at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:187)
 at java.lang.reflect.Method.invoke(Native Method)
 at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1136)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:773)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:750)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:256)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
 at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBeanServerImpl_WLSkel.java:1075)
 at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
 at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
 at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 <Jun 14, 2001 4:56:39 PM CDT> <Error> <Cluster> <Conflict start: You tried to
 bind an object under the name HelloWorldBean_EO in the jndi tree. The object you
 have bound weblogic.rmi.cluster.ClusterableRemoteObject from prodlogic2 is non
 clusterable and you have tried to bind more than once from two or more servers.
 Such objects can only deployed from one server.>

Event Log Replication on Cluster Server (MS Server 2003)

Please help me about the EnableEventLogReplication on SERVER 2003. I just saw the recommended on MS support about it.
"If the EnableEventLogReplication registry entry is set to 1, the cluster node replicates events in the event log to all other nodes in the cluster. Tools that monitor multiple
servers, report a single event multiple times, one time from each node. "
I have got the problem about event logs replicates and hard to summary event logs on all nodes. If I want to disable this function I would like to know the effect about this one. it will not replicates events and will not get any worse cases on the server
that my customer using? Could you please advise?

As you mentioned, if you disable EnableEventLogReplication, Event Log Replication will be disable for one or more node in the cluster or the entire cluster. One or more cluster node is down or has experienced a failure, and preventing Event Log Replication
from taking place.
Note: if you disable the replication at a specific node, replication of events from that node to other nodes is disabled. Other nodes that have the EnableEventLogReplication property turned on still replicate to that node. This only replicates the System,
Application and Security event logs.
http://support.microsoft.com/kb/229071/en-us
http://support.microsoft.com/default.aspx?kbid=224969

JNDI replication and rebinging from multiple servers

Here is what I need:
Server1 binds ObjX to it's JNDI tree (which replicates the object to the
other servers in the cluster)
Server2 does a lookup on ObjX, changes some values and rebinds it back to
it's JNDI tree (which should replicate the changes to the other servers
including Server1).
The above does not happen because, Server1 is known to be the owner of ObjX,
and thus instead of getting replicated data after Server2 rebinds, it gets
duplicate name errors.
Is there anyway to make the above work the way I want it to?

It is bad to use JNDI to replicate application data/cache in the cluster.
If you are sure that you want to use multicast to replicate your data,
in 6.0 you can use JMS:
http://e-docs.bea.com/wls/docs60/jms/implement.html#1206428
Or you can use javagroups: http://sourceforge.net/projects/javagroups
John Boyd <[email protected]> wrote:
Yes, exactly.
"Dimitri Rakitine" <[email protected]> wrote in message
news:[email protected]..
Are you trying to use JNDI to replicate runtime data across the cluster?
John Boyd <[email protected]> wrote:
Here is what I need:
Server1 binds ObjX to it's JNDI tree (which replicates the object to the
other servers in the cluster)
Server2 does a lookup on ObjX, changes some values and rebinds it back
to
it's JNDI tree (which should replicate the changes to the other servers
including Server1).
The above does not happen because, Server1 is known to be the owner of
ObjX,
and thus instead of getting replicated data after Server2 rebinds, itgets
duplicate name errors.
Is there anyway to make the above work the way I want it to?--
Dimitri
Dimitri

How to lookup the remote interface in JNDI of the cluster (glassfish)

I have write a simple sessionbean:
package authority;
import javax.ejb.Stateless;
* Session Bean implementation class LoginSessionBean
@Stateless
public class LoginSessionBean implements LoginSessionBeanRemote, LoginSessionBeanLocal {
     * Default constructor.
    public LoginSessionBean() {
        // TODO Auto-generated constructor stub
    @Override
    public boolean login(String name, String password)
        boolean result = false;
        System.out.println("User: " + name + " is login with password: " + password);
        return result;
    @Override
    public LoginSessionBeanRemote create()
        // TODO Auto-generated method stub
        return this;
}And I write a simple client to test it.
package test;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;
import authority.LoginSessionBean;
import authority.LoginSessionBeanRemote;
public class SessionBeanTestClient
    public static void main(String[] args)
        try
            InitialContext context = new InitialContext();
            Object obj = context.lookup(LoginSessionBean.class.getName());
            LoginSessionBeanRemote loginService = (LoginSessionBeanRemote)PortableRemoteObject.narrow(obj, LoginSessionBeanRemote.class);
            loginService.login("Jason", "password");
        catch (NamingException e)
            // TODO Auto-generated catch block
            e.printStackTrace();
}And it is OK, but after I deploy the sessionbean into a cluster with two instances on local host, it can not find the remote interface:
javax.naming.NameNotFoundException: authority.LoginSessionBean not found
     at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)Is it different for cluster (for IIOP port?), I want to test the HA solution, how could I start it?

Please look at http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-how-to.html. There is a How-To on local interface.
thanks
Debu

URL Resource and JNDI Replication

Do URLResources get replicated in the JNDI tree?

JDBC resource can be created using asadmin command.
Its a two step process.
First JDBC connection pool has to be created using following command.
asadmin create-jdbc-connection-pool user admin password adminadmin host fuyako port 7070 datasourceclassname XA restype jax.sql.DataSource
isolationlevel serializable isconnectvalidatereq=true validationmethod auto-commit description "XA Connection" --property DatabaseName="jdbc\:pointbase\:server\:\/\/local
host\/sample" :User=public:Password=public XA_connection_pool
Next JDBC resource has to be created using the following command.
asadmin create-jdbc-resource --user admin --password adminadmin --host fuyako --port 7070
--connectionpoolid XA_connection_pool --description
"creating a sample jdbc resource" sample_jdbc_resource
Please change the parameters as suitable to you.
The detailed description of these commands can be found as following URLs
http://java.sun.com/j2ee/1.4/docs/relnotes/cliref/hman1/create-connector-connection-pool.1.html
http://java.sun.com/j2ee/1.4/docs/relnotes/cliref/hman1/create-jdbc-resource.1.html

Jndi tree different in different servers in a cluster?

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

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

JNDI replication in cluster

Similar Messages

Maybe you are looking for