Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sporadic startup failure on 3.6-EA #6684

Closed
nilskp opened this issue Nov 6, 2015 · 2 comments
Closed

Sporadic startup failure on 3.6-EA #6684

nilskp opened this issue Nov 6, 2015 · 2 comments
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Defect
Milestone

Comments

@nilskp
Copy link
Contributor

nilskp commented Nov 6, 2015

Have seen this a few times when testing locally (using 3 Hz instances + 1 client in same JVM), on 3.6-EA:

Nov 06, 2015 3:16:19 PM com.hazelcast.cluster.impl.operations.FinalizeJoinOperation
SEVERE: [169.254.24.193]:5701 [622fac90-2834-486b-8b7b-aae59343dab8] [3.6-EA] Cannot set initial state after node joined! -> ACTIVE
java.lang.IllegalStateException: Cannot set initial state after node joined! -> ACTIVE
    at com.hazelcast.cluster.impl.ClusterServiceImpl.initialClusterState(ClusterServiceImpl.java:877)
    at com.hazelcast.cluster.impl.operations.FinalizeJoinOperation.run(FinalizeJoinOperation.java:71)
    at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:167)
    at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:386)
    at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:184)
    at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:137)
    at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:124)
    at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:99)
@jerrinot jerrinot added this to the 3.6 milestone Nov 6, 2015
@mdogan
Copy link
Contributor

mdogan commented Nov 7, 2015

Please try latest master. This should have been fixed already by #6540

@enesakar
Copy link
Contributor

closing. please re-open if you see #6540 did not solve this

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Defect
Projects
None yet
Development

No branches or pull requests

5 participants