This content has been marked as final.
Show 3 replies
-
1. Re: Several applications running in the same instance
jaikiran Jul 4, 2009 10:22 AM (in response to chkiron)"chkiron" wrote:
My company is building 3 different applications (3 .WARs). Today, they use the same libs version (spring, hibernate, rich-faces, etc).
My client' IT staff wants to put these 3 applications and any others they have or are building in the same JBoss instance.
I am trying to change this, but I am lacking arguments.
I don't see anything wrong in hosting all those 3 apps on the same server instance. As long as you have ensured proper classloader isolation (so that each app uses its own version of the libraries that's packaged within the app), i think there shouldn't be any issues. Here's some wiki links for classloader related details:
http://www.jboss.org/community/wiki/JbossClassLoadingUseCases
http://www.jboss.org/community/wiki/classloadingconfiguration -
2. Re: Several applications running in the same instance
chkiron Jul 4, 2009 12:56 PM (in response to chkiron)Hi, Jaikiran!
Thank you for your answer!"jaikiran" wrote:
I don't see anything wrong in hosting all those 3 apps on the same server instance.
I had some troubles with this scenario before. Let's say appl A and appl B both use the same version of library X and are running in the production server. A project later and the library X's version in appl B is completely updated. In this case, I had several problems of class colision in the server and had to use the same X version in both applications."jaikiran" wrote:
As long as you have ensured proper classloader isolation (so that each app uses its own version of the libraries that's packaged within the app), i think there shouldn't be any issues.
I will study the links you provided, thank you! -
3. Re: Several applications running in the same instance
jaikiran Jul 5, 2009 2:10 PM (in response to chkiron)"chkiron" wrote:
I had some troubles with this scenario before. Let's say appl A and appl B both use the same version of library X and are running in the production server. A project later and the library X's version in appl B is completely updated. In this case, I had several problems of class colision in the server and had to use the same X version in both applications.
That's exactly what the classloader scoping (the links in my previous reply) will solve.