|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Cluster
Submitted by visamal on Mon, 06/29/2009 - 17:53.
Hi, Clustering is with more than one application server. My qs:
a) How can we maintain single instance model / no duplicate instance across JVM (without terracota server)
b) Do we need any programatic code required for single instance (like keep the db locked and do not allow second server to create instance?
c) If my load balancer (app server level& hardware level) is perfect, still do we need any program/ code to handle?
thanks in adv.
Viswa.