1 of 1 people found this helpful
2) No (well, you could run multiple JBoss AS instances and deploy one app to each)
3) Not sure what the question was here... But your assumption appears to be correct regarding separation of dev/test/production.
4) With one app per app server you have the ability to configure each one to your liking, and there is the redued risk of conflicts, and if one app goes down it will not effect other apps. Usually having only one app per app server is a good idea for "significant" apps that have numerous users and get a lot of use. The down side is that each app server instance potentially uses a lot of memory.
Thanks for your response Peter.
I'm still confused by your 'no' answer to question number two.
I know a system admin ( not a JBoss Admin) who claims he can start different apps ( two WAR files for example) under one
JBoss instance and each of these apps is run under a separate JVM and each is bound to separate ports. He says he does this
by scripting the setting:
JAVA_OPTS = $JAVA_OPTS -Djboss.platform.mbeanserver
How can I prove or disprove that the app is running under a new JVM ?
The only thing that -Djboss.platform.mbeanserver does is tells JBoss AS to use the MBean server built into the JVM instead of using its own. This option is typically used so that you can access the MBeans via JConsole or similar tools. See:
This option does not cause apps to be deployed into separate JVMs.
You can bind different apps to different ports using virtual hosts:
But the apps are still running under the same JVM.
You can tell how many JVMs are running by looking at the java processes (I could be more spcific if I knew the OS). Or you could use the jps utility that comes with the JDK.
Thanks for your help........