Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Assuming you have a productive java application and don't want to have (even small) downtimes for software updates (including updated .class files) to take effect.

What infrastructure / server / tools do you use to achieve this?

Any experiences are much appreciated! Could be anything like two servers where one is updated while the other does the "old" job, features of e.g. a Tomcat server or tools enabling this.

share|improve this question
up vote 0 down vote accepted

It's not entirely clear from your description, but I'm guessing you're talking about Java EE and not Java SE applications? Java SE, we just use JNLP for deployment. Java EE, where we use Glassfish as the container and it has an option to install a new version without interrupting current sessions. We're not super heavy users, so I'm not absolutely positive that it has prevented an issue, but we've never had an issue. Our Tomcat EE users just get rudely bumped periodically when we do updates and are used to it at this point. :-(

share|improve this answer
Thanks for the insight! Actually I wasn't so much aware about the difference between Java SE and Java EE; I'm just using grails which I think is based on Java SE(?). – Joe Sep 17 '10 at 6:43
To make it simple: J2SE = Client softwares, J2EE = Server software that runs on an application server – Kedare Oct 22 '10 at 20:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.