[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1520
  • Last Modified:

Problems related to unbind of jndi in weblogic cluster.

I have 4 Weblogic 9.2 servers in cluster.

And the JNDIs are maintained in the weblogic cluster, using the following code:
Hashtable ht = new Hashtable();
ht.put(WLContext.REPLICATE_BINDINGS, "true");
ht.put(WLContext.ALLOW_EXTERNAL_APP_LOOKUP, "true");
ht.put(WLContext.ALLOW_GLOBAL_RESOURCE_LOOKUP, "true");
Context ctx= new InitialContext(ht);

While adding the new jdni property works absolutely fine (when a new property is added on one server it gets reflected onto the other servers in the cluster).

The deletion of the jndi property thats giving problems, the property is removed only from the server where the property deletion is initiated, it remains as it is on other servers.

what I suspect is that Context.unbind() id not propogated accross the servers in cluster as it is in the case of context.bind(), need help in the matter and its kinda urgent.

Thanks - humanonomics.
0
humanonomics
Asked:
humanonomics
  • 2
  • 2
1 Solution
 
RajeshpolaCommented:
Hi ,

Here we have to consider few points, above code snippet is present in u r application code right ? If you better undeploy the application and delete the temporary files and then deploy. If the cluster communication is workign properly then, it all the managed servers in the clusters should update their local JNDI Tree with Cluster level JNDI.

Is the clustering happening properly in other areas like .... r u able to replicate u r sessions ?

Other wise you can increase the logging level to get more information from the servers or please test your multicast communcation.

-Rajesh  

0
 
humanonomicsAuthor Commented:
found the solution, rather the root of the problem, the weblogic implementation of jndi works in following manner:
for adding new JNDI, its replicated properly accross all the servers.
For Deletion (unbind) and updation (rebind), the replication works in a selective way, if the property is added via say server1, and if the property is deleted / updated on server1 then it will be reflected accross all the servers. But if a property is added via server1 and updated/deleted via server2 then, it will not be reflected accross the cluster, will only change stuff on server2.

right now I am working on the work around.

Thanks -- humanonomics
0
 
RajeshpolaCommented:
thanks for the info.
0
 
humanonomicsAuthor Commented:
no problem :-)
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now