Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Weblogic Clustering and load balancing

 
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to create a weblogic cluster with two managed servers but as our application has Static HashMaps,singleton classes etc which are updating in each transaction. So i want to know whether a memory replication is possible so that in case of failover or load balacing this data should be shared by both the servers.
 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

nandkishor ra
our application has Static HashMaps,singleton classes etc which are updating in each transaction.



Well ya had me, until you said "Updating in each transaction."

Yes Weblogic does have the means through it's Replicated JNDI Naming Space, to share some distributed objects, but the objects are not transaction aware.

It sounds like this is persistent state data. I have modeled this situation in the past with a Meta Data Schema in a database. Often not the same database/vendor as my main application (Good separation - Application/Business data in one data store, Application Meta or state data in another data store). The benefits of this approach is that the data store is shared among as many managed servers as you need, and with Java Persistence Architecture (JPA) - (KODO/Open JPA) and a perhaps @version tag, this is a proven solution that will scale to as many managed severs as you need with transaction awareness.

Just 1 on many possible solutions.

Tony
Sun Certified Web Business Component Developer
Sun Certified Web Components Developer
Sun Certified Programmer for the Java 2 Platform
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic