[
https://jira.jboss.org/jira/browse/EMBJOPR-43?page=com.atlassian.jira.plu...
]
John Mazzitelli closed EMBJOPR-43.
----------------------------------
Resolution: Deferred
While the idea presented in this JIRA is most definitely valid and something we want to
do, it is not appropriate to be here in the EMBJOPR project. It is more appropriate in
JOPR (since it involves the JBossAS plugin) and probably even more appropriate to be in
the RHQ JIRA project since this probably will require enhancements to the RHQ core.
Easy management of multiple JBoss AS instance for process isolation
-------------------------------------------------------------------
Key: EMBJOPR-43
URL:
https://jira.jboss.org/jira/browse/EMBJOPR-43
Project: Embedded Jopr
Issue Type: Feature Request
Reporter: Francisco Jose Peredo Noguez
Since java has no real process isolation, a misbehaved JEE application can bring down an
entire server (if it has a bug with an infinite-loop for example, or simply because each
time applications are undeployed the JVM is no able to really reclaim all the memory
spaced because of bugs inherent in the JVM design). In OAS (Oracle Application Server)
this problem is solved by using multiple instances, this is of course possible in JBoss
(nobody prevents you from running several instances of Jboss in your server) but has to be
done manually. I would like to see an option in Jopr UI where I could just click a button
saying: "Create new JBoss Instance" and then be able to "Tranfer selected
applications to another Jboss Instance" that way related applications can be kept in
the same instance, and unrelated ones can be kept in different instances that can be
restarted independently if the misbehave.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira