[
https://jira.jboss.org/jira/browse/JOPR-77?page=com.atlassian.jira.plugin...
]
Heiko W. Rupp resolved JOPR-77.
-------------------------------
Resolution: Done
rev 197
QA: please test restart on boxes other then RHEL too - especially to see if there may be
lingering ports around - meaning that the start after stop fails, because a port is
reported as being stil in use.
If this happens, we need to wait some time between stop() and start() in restart.
JBAS restart op should be fail fast, otherwise you get dup processes
started
----------------------------------------------------------------------------
Key: JOPR-77
URL:
https://jira.jboss.org/jira/browse/JOPR-77
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Affects Versions: 2.1
Environment: linux, postgres, upgraded install, jon2.1CR2 build
Reporter: Jeff Weiss
Assignee: Heiko W. Rupp
Priority: Critical
Fix For: 2.2
Start EAP4.3 production, import the resource
Don't fix the connection property error, go to Operations, do a Restart.
It will eventually be shown "Success".
Check the process list on the machine and note there are now 2 EAP processes running -
the first never got shut down properly because of the lack of auth credentials in the
connection properties.
<joseph> lookin' at the code i think you're right. we blindly catch
shutdown errors and continue start afterwards
kind of silly. all ops should be fail fast
--
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