Exception while starting new node and node-info deployed in farm directory
Reported by Deleted User | July 31st, 2009 @ 06:02 AM | in 1.0.0.Beta8
Here are steps to reproduce his errors: http://gist.github.com/159260. Here is full server log: http://gist.github.com/159232
node-info.war is available here: http://repo.oddthesis.org/node-info/node-info.war
Second thing: back-end instances had shut down JBoss AS instances!
Comments and changes to this ticket
-
Deleted User July 31st, 2009 @ 06:30 AM
- State changed from “new” to “open”
Confirmed also with latest Beta7-SNAPSHOT AMIs
Full log: http://gist.github.com/159303
On Beta7-SNAPSHOT JGroups 2.6.12.Beta1 was installed: on front-end (GossipRouter) and in back-end (JBoss AS).
-
Deleted User July 31st, 2009 @ 11:08 PM
I found a thread on the web. Could it help?
http://www.nabble.com/Cluster-node-failing-to-start-properly-after-...
-
Deleted User August 9th, 2009 @ 10:13 PM
I cannot reproduce bug with first smoke test with Beta7-SNAPSHOT. Need more testing.
-
Deleted User August 10th, 2009 @ 07:14 AM
Another day, another stacktrace... It looks identical: http://gist.github.com/165290
-
Deleted User August 21st, 2009 @ 04:27 AM
- State changed from “open” to “resolved”
Could not reproduce in latest build.
-
Deleted User October 2nd, 2009 @ 11:41 PM
- Milestone changed from “1.0.0.Beta7” to “1.0.0.Beta8”
- State changed from “resolved” to “open”
-
-
Manik Surtani October 12th, 2009 @ 01:59 AM
- Tag changed from “gossip router, as5, bug” to “gossip router, jboss cache, state transfer, as5, bug”
Hmm, version of JBoss Cache used?
-
Deleted User October 12th, 2009 @ 02:41 AM
This is default shipped with JBoss AS 5.1.0.GA: 3.1.0.GA.
-
Manik Surtani October 12th, 2009 @ 02:44 AM
Is this easily reproducible? And if so, could you try with the latest JBoss Cache (3.2.1.GA)? Should be a drop-in replacement for 3.1.0.
-
Deleted User October 12th, 2009 @ 04:20 AM
I just got another e-mail confirming that this happens. The problem is that it sometimes exists, sometimes not - that's really strange. I couldn't find the cause for that issue :/
I'll try latest JBoss Cache.
-
Deleted User November 4th, 2009 @ 07:18 AM
After I upgraded to latest JBoss Cache the problem still exists... Manik, Bela?
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
**We moved**
Read more here: http://community.jboss.org/docs/DOC-14372
Manik Surtani