[
http://jira.jboss.com/jira/browse/JBCLUSTER-156?page=comments#action_1234... ]
Samuel commented on JBCLUSTER-156:
----------------------------------
The problem is repeatedly reproducible in Windows XP Prof, Service Pack 2 with Java
1.5.0_09 and JBoss 4.0.3GA
Machine A: Start run -c all
Machine B Start run -c all
Do a Farm deployment one war file in Machine A
Farm deployment transferred the deployment to B
Take down JBoss in Machine A.
Hold for some time
Start JBoss in Machine A
No forum is required for Critical issue. It is not the user error. User need to go forums
only if he is not aware of what he is doing.
Bringing down a OS is a critical for JBoss as well as the OS
More than this there is no detailed information needed because this simple scenario fails
critically.
It is reproducible in many XP machines
JBoss clustering start reboots machine
--------------------------------------
Key: JBCLUSTER-156
URL:
http://jira.jboss.com/jira/browse/JBCLUSTER-156
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: JBOSS 4.0.3, Java 5,XP professional
Reporter: Samuel
Assigned To: Brian Stansberry
Priority: Blocker
I was setting up clustering and ran JBoss app server with run -c all option.
First time it ran fine. Well and good. Then I shutdown the server. Re-launched run -c all
and when the server brings up it reboots my windows xp.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira