This week's book giveaway is in the Performance forum. We're giving away four copies of The Java Performance Companion and have Charlie Hunt, Monica Beckwith, Poonam Parhar, & Bengt Rutisson on-line! See this thread for details.
I have a problem regarding to the software deployment. We're using JBoss 4.2.3.
Please let me explain a typical manual deployment process I'm doing now:
1. Copy EARs, WARs and JARs to server.
2. Stop server.
3. Copy EARs, WARs and JARs to deploy folder.
4. Run database update script.
5. Start server.
I was looking for a way to avoid the server restart. Because it caused a lot of problem and a lot of inconvenience. For example, I had to send emails to a big list in order to schedule a server down time.
The other problem is, we have 2 servers which communicate with each other remotely via SOAP, if one server goes down, it will likely cause some data synchronization problems.
The hot deployment didn't really work for me. Sometimes I got class loaders exceptions, and sometimes cache issues.
I was considering clustering but not quite sure if it would work or not.
Does anyone have any similar experience? Any solutions or suggestions?