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

No remote message handler registered for this message #1015

Closed
zlatinb opened this issue Apr 13, 2019 · 0 comments
Closed

No remote message handler registered for this message #1015

zlatinb opened this issue Apr 13, 2019 · 0 comments
Labels
archived Archived issues from the legacy Java implementation of Atomix legacy Issues from the legacy Java implementation of Atomix

Comments

@zlatinb
Copy link

zlatinb commented Apr 13, 2019

Expected behavior

The CompletableFuture for start()-ing Atomix to return from join()

Actual behavior

The join() call never returns, and in the logs at FINE level I see the following:

FINE: RaftClient{system-partition-1} - OpenSessionRequest{node=mainNode, serviceName=atomix-primary-elector, serviceType=PRIMARY_ELECTOR, readConsistency=SEQUENTIAL, minTimeout=250, maxTimeout=30000} failed! Reason: io.atomix.cluster.messaging.MessagingException$NoRemoteHandler: No remote message handler registered for this message

Steps to reproduce

Start several Atomix instances on different hosts

Minimal yet complete reproducer code (or URL to code)

https://gist.github.com/zlatinb/a84518bde5d13fab21b144da3111b816

Environment

  • Atomix: 3.0.8 and 3.1.5
  • OS: OSX and Linux
  • JVM 11.0.2
@kuujo kuujo closed this as completed Jan 13, 2023
@kuujo kuujo added archived Archived issues from the legacy Java implementation of Atomix legacy Issues from the legacy Java implementation of Atomix labels Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archived Archived issues from the legacy Java implementation of Atomix legacy Issues from the legacy Java implementation of Atomix
Projects
None yet
Development

No branches or pull requests

2 participants