[ http://jira.jboss.com/jira/browse/JBCLUSTER-156?page=all ] Brian Stansberry resolved JBCLUSTER-156. ---------------------------------------- Resolution: Incomplete Description Use the forums for help. -- 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

[ 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 -- 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

[ http://jira.jboss.com/jira/browse/JBCLUSTER-156?page=all ] Brian Stansberry updated JBCLUSTER-156: --------------------------------------- Priority: Major (was: Blocker) Attach the boot.log and server.log from Machine A. Don't touch the priority; you're not a committer. -- 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

[ http://jira.jboss.com/jira/browse/JBCLUSTER-156?page=all ] Brian Stansberry updated JBCLUSTER-156: --------------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97709 I am not able to reproduce this using the steps provided. Please continue the discussion on the forum thread you opened. I should not have used the words "Use the forums for help" above. I should have said "Open a forum thread where we can isolate the issue to something reproducible; once we've done that and found it's a JBoss problem we can re-open this JIRA or open a new, more focused one." Our practice is not to use JIRA for that kind of discussion; that's what the forums are for. I knew your original description was not trivially reproducible, as I've done the steps described in the initial post many times on 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

[ http://jira.jboss.com/jira/browse/JBCLUSTER-156?page=all ] Samuel updated JBCLUSTER-156: ----------------------------- Environment: JBOSS 4.0.3, Java 5.0.06,07,08,09,10,XP professional (was: JBOSS 4.0.3, Java 5,XP professional) Description: The cluster start fails with JRE 6 rel 06-10. Note: No Problem with with Java 1.5.0.05. Fails in two places randomly 1. While Loading the JUddi Services 2. After GMS-JGroups membership broadcasting and farm deploy sync Not only JBoss Crash The Windows XP crash. Reproducable in all XP Machine running SP 1 and 2 atleast in my development environment/team. Set up clustering and run JBoss app server with run -c all option. First time it will run fine as long as farm deploy dir is empty. Well and good. Then shutdown the server. Re-launched run -c all and you will see the server brings up it reboots Windows XP. was: 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

[ http://jira.jboss.com/jira/browse/JBCLUSTER-156?page=comments#action_1235... ] Brian Stansberry commented on JBCLUSTER-156: -------------------------------------------- Over the past few months I've made several attempts at reproducing this, always without success. If anyone is seeing this consistently, please enable DEBUG logging for org.jgroups, post the boot.log and server.log from all servers involved, and please post the output from ipconfig /all as well. -- 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

[ http://jira.jboss.com/jira/browse/JBAS-5420?page=all ] Brian Stansberry updated JBAS-5420: ----------------------------------- Component/s: Clustering Affects Version/s: JBossAS-4.0.3 Final Moved this to the JBAS project; added Affects Version 4.0.3 as that is what the initial report stated. -- 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