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

AsynchronousCloseException when a Cassandra node joins cluster

SA-61253

Summary



AsynchronousCloseException when the node that should be used for Data Decision Store (Cassandra) attempts to not join the cluster.


Error Messages



java.nio.channels.AsynchronousCloseException: null
at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:223) ~[na:1.8.0]
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:492) ~[na:1.8.0]
at org.apache.cassandra.io.util.DataOutputStreamAndChannel.write(DataOutputStreamAndChannel.java:48) ~[apache-cassandra-2.1.14.jar:2.1.14]
at org.apache.cassandra.streaming.ConnectionHandler$MessageHandler.sendInitMessage(ConnectionHandler.java:191) ~[apache-cassandra-2.1.14.jar:2.1.14]
at org.apache.cassandra.streaming.ConnectionHandler.initiate(ConnectionHandler.java:81) ~[apache-cassandra-2.1.14.jar:2.1.14]



Steps to Reproduce



Attempt to add a node to the cluster.


Root Cause



A defect or configuration issue in the operating environment. The JVM used for Cassandra is an IBM JVM, which has issues with Cassandra.


Resolution

  1. Apply HFix-44049
  2. Reference an Oracle or OpenJDK JVM instead of the IBM one

 

Suggest Edit

Published July 24, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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