Hot vs Cold Deployment in JBoss

Hot vs Cold Deployment 

Hot deployment is cool, but there is a risk of:

1. Class-Loader exceptions (more on this later)
2. Unrecognized configuration settings
3. Lost session/application scoped data

To enrich your career and become a JBoss professional, visit Tekslate, the global online training platform:"JBoss Training". This course will help you achieve excellence in this field.

Cold deployment is slow but stable

1. Stop JBoss AS
2. Optionally delete data/, log/, tmp/, work/
3. Redeploy your application(s)
4. Start JBoss AS

Hot deployment is generally considered safe for:

1. Java Server Pages (.jsp) files. They get recompiled automatically by the servlet engine following a change.
2. Class files that do not change their public interfaces, especially when there is no RMI involved. This requires full redeployment, so it is still somewhat risky.

For an in-depth understanding on JBoss click on:

• JBoss architecture
• Installation of jboss
• Session Configuration
• JBoss Overview
• Loggin in JBoss