Exception while starting new node and node-info deployed in farm directory
-
Deleted User- 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
I found a thread on the web. Could it help?
http://www.nabble.com/Cluster-node-failing-to-start-properly-after-...
-
Deleted User
I cannot reproduce bug with first smoke test with Beta7-SNAPSHOT. Need more testing.
-
Deleted User
Another day, another stacktrace... It looks identical: http://gist.github.com/165290
-
-
Deleted User
- Milestone changed from 1.0.0.Beta7 to 1.0.0.Beta8
- State changed from resolved to open
-
-
Manik Surtani
- Tag changed from gossip router, as5, bug to gossip router, jboss cache, state transfer, as5, bug
Hmm, version of JBoss Cache used?
-
Deleted User
This is default shipped with JBoss AS 5.1.0.GA: 3.1.0.GA.
-
Manik Surtani
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
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
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.