Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Hazelcast exception when starting the server

SA-40138

Summary



Hazelcast exception when starting the server.

Error Messages



[6/15/17 21:16:40:511 EDT] 00000027 TcpIpConnecti I com.hazelcast.nio.tcp.TcpIpConnection [your_ip]:5703 [9f353e11664cd839a2abd71f71369ded] [3.4.1] Connection [your_host/your_ip:47901] lost. Reason: java.lang.IllegalArgumentException[Packet versions are not matching! This -> 3, Incoming -> 1]
[6/15/17 21:16:40:512 EDT] 00000027 ReadHandler W com.hazelcast.nio.tcp.ReadHandler [your_ip]:5703 [9f353e11664cd839a2abd71f71369ded] [3.4.1] hz._hzInstance_1_9f353e11664cd839a2abd71f71369ded.IO.thread-in-1 Closing socket to endpoint null, Cause:java.lang.IllegalArgumentException: Packet versions are not matching! This -> 3, Incoming -> 1
java.lang.IllegalArgumentException: Packet versions are not matching! This -> 3, Incoming -> 1
at com.hazelcast.nio.Packet.readFrom(Packet.java:148)
at com.hazelcast.nio.tcp.DefaultPacketReader.readPacket(DefaultPacketReader.java:45)
at com.hazelcast.nio.tcp.SocketPacketReader.read(SocketPacketReader.java:41)
at com.hazelcast.nio.tcp.ReadHandler.handle(ReadHandler.java:79)
at com.hazelcast.nio.tcp.InSelectorImpl.handleSelectionKey(InSelectorImpl.java:49)
at com.hazelcast.nio.tcp.AbstractIOSelector.handleSelectionKeys(AbstractIOSelector.java:159)
at com.hazelcast.nio.tcp.AbstractIOSelector.run(AbstractIOSelector.java:132)


Steps to Reproduce



Restart the Server


Root Cause



A defect or configuration issue in the operating environment

The machine is host to two independent clusters. The error should resolve itself, but may take considerable time and 'conversation' between nodes. It can be avoided using the change below.


Resolution



Make the following change to the operating environment:

Specify distinct port ranges for the clusters, the range specification looks like this - you can pick any port range you like that is open. Once established at startup only one port is used to communicate.
<env name=“cluster/hazelcast/ports” value=“5701-5749” /> <-- port range for cluster 1
<env name=“cluster/hazelcast/ports” value=“5750-5799” /> <-- port range for cluster 2

Published August 26, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us