com.datastax.driver.core.exceptions.DriverInternalError

Unexpected error while processing response from /xxxxxxx:9042

Samebug tips0

There are no available Samebug tips.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via by Olivier Michallat,
  • via by Fabrice Larcher,
  • Stack trace

    • com.datastax.driver.core.exceptions.DriverInternalError: Unexpected error while processing response from /xxxxxxx:9042 at com.datastax.driver.core.exceptions.DriverInternalError.copy(DriverInternalError.java:42) at com.datastax.driver.core.DefaultResultSetFuture.extractCauseFromExecutionException(DefaultResultSetFuture.java:258) at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:174) at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:52)[...] Caused by: com.datastax.driver.core.exceptions.DriverInternalError: Unexpected error while processing response from /xxxxxxxxx:9042 at com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:120) at com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandler.java:237) at com.datastax.driver.core.RequestHandler.onSet(RequestHandler.java:261) at com.datastax.driver.core.Connection$Dispatcher.messageReceived(Connection.java:645)[...] Caused by: java.lang.NullPointerException at com.datastax.driver.core.ArrayBackedResultSet.checkWasApplied(ArrayBackedResultSet.java:414) at com.datastax.driver.core.ArrayBackedResultSet.<init>(ArrayBackedResultSet.java:51) at com.datastax.driver.core.ArrayBackedResultSet.<init>(ArrayBackedResultSet.java:36) at com.datastax.driver.core.ArrayBackedResultSet$SinglePage.<init>(ArrayBackedResultSet.java:165) at com.datastax.driver.core.ArrayBackedResultSet$SinglePage.<init>(ArrayBackedResultSet.java:156) at com.datastax.driver.core.ArrayBackedResultSet.fromMessage(ArrayBackedResultSet.java:81) at com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:105) ... 4 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    No Bugmate found.