Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

failed: CassandraClusteredPersistentEntitySpec

See original GitHub issue

Another flaky test: https://travis-ci.org/lagom/lagom/jobs/174684362

[JVM-3] Exception encountered when invoking run on a nested suite - barrier failed: cassandra-started *** ABORTED ***
[JVM-3]   java.lang.RuntimeException: barrier failed: cassandra-started
[JVM-3]   at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:210)
[JVM-3]   at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:185)
[JVM-3]   at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
[JVM-3]   at akka.actor.FSM$class.processEvent(FSM.scala:663)
[JVM-3]   at akka.remote.testconductor.ClientFSM.akka$actor$LoggingFSM$$super$processEvent(Player.scala:145)
[JVM-3]   at akka.actor.LoggingFSM$class.processEvent(FSM.scala:799)
[JVM-3]   at akka.remote.testconductor.ClientFSM.processEvent(Player.scala:145)
[JVM-3]   at akka.actor.FSM$class.akka$actor$FSM$$processMsg(FSM.scala:657)
[JVM-3]   at akka.actor.FSM$$anonfun$receive$1.applyOrElse(FSM.scala:651)
[JVM-3]   at akka.actor.Actor$class.aroundReceive(Actor.scala:484)
[JVM-3]   ...
[JVM-2] Exception encountered when invoking run on a nested suite - barrier failed: cassandra-started *** ABORTED ***
[JVM-2]   java.lang.RuntimeException: barrier failed: cassandra-started
[JVM-2]   at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:210)
[JVM-2]   at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:185)
[JVM-2]   at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
[JVM-2]   at akka.actor.FSM$class.processEvent(FSM.scala:663)
[JVM-2]   at akka.remote.testconductor.ClientFSM.akka$actor$LoggingFSM$$super$processEvent(Player.scala:145)
[JVM-2]   at akka.actor.LoggingFSM$class.processEvent(FSM.scala:799)
[JVM-2]   at akka.remote.testconductor.ClientFSM.processEvent(Player.scala:145)
[JVM-2]   at akka.actor.FSM$class.akka$actor$FSM$$processMsg(FSM.scala:657)
[JVM-2]   at akka.actor.FSM$$anonfun$receive$1.applyOrElse(FSM.scala:651)
[JVM-2]   at akka.actor.Actor$class.aroundReceive(Actor.scala:484)
[JVM-2]   ...
[JVM-2] Run completed in 38 seconds, 296 milliseconds.
[JVM-2] Total number of tests run: 0
[JVM-2] Suites: completed 0, aborted 1
[JVM-2] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[JVM-2] *** 1 SUITE ABORTED ***
[JVM-3] Run completed in 38 seconds, 51 milliseconds.
[JVM-3] Total number of tests run: 0
[JVM-3] Suites: completed 0, aborted 1
[JVM-3] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[JVM-3] *** 1 SUITE ABORTED ***
[JVM-1] 2016-11-10 04:50:25,489 ERROR akka.actor.OneForOneStrategy - timeout while waiting for barrier 'cassandra-started'
[JVM-1] akka.remote.testconductor.BarrierCoordinator$BarrierTimeout: timeout while waiting for barrier 'cassandra-started'
[JVM-1] 2016-11-10 04:50:32,538 INFO  com.datastax.driver.core.utils.UUIDs - PID obtained through native call to getpid(): 15721
[JVM-1] Exception encountered when invoking run on a nested suite - barrier failed: cassandra-started *** ABORTED ***
[JVM-1]   java.lang.RuntimeException: barrier failed: cassandra-started
[JVM-1]   at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:210)
[JVM-1]   at akka.remote.testconductor.ClientFSM$$anonfun$3.applyOrElse(Player.scala:185)
[JVM-1]   at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
[JVM-1]   at akka.actor.FSM$class.processEvent(FSM.scala:663)
[JVM-1]   at akka.remote.testconductor.ClientFSM.akka$actor$LoggingFSM$$super$processEvent(Player.scala:145)
[JVM-1]   at akka.actor.LoggingFSM$class.processEvent(FSM.scala:799)
[JVM-1]   at akka.remote.testconductor.ClientFSM.processEvent(Player.scala:145)
[JVM-1]   at akka.actor.FSM$class.akka$actor$FSM$$processMsg(FSM.scala:657)
[JVM-1]   at akka.actor.FSM$$anonfun$receive$1.applyOrElse(FSM.scala:651)
[JVM-1]   at akka.actor.Actor$class.aroundReceive(Actor.scala:484)
[JVM-1]   ...
[JVM-1] Run completed in 45 seconds, 169 milliseconds.
[JVM-1] Total number of tests run: 0
[JVM-1] Suites: completed 0, aborted 1
[JVM-1] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[JVM-1] *** 1 SUITE ABORTED ***
[JVM-1] 2016-11-10 04:50:32,892 ERROR com.datastax.driver.core.ControlConnection - [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
[JVM-1] 2016-11-10 04:50:32,916 ERROR com.datastax.driver.core.ControlConnection - [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
[JVM-1] 2016-11-10 04:50:33,893 ERROR com.datastax.driver.core.ControlConnection - [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
[JVM-1] 2016-11-10 04:50:33,925 ERROR com.datastax.driver.core.ControlConnection - [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
[error] Failed: com.lightbend.lagom.scaladsl.persistence.cassandra.CassandraClusteredPersistentEntitySpecMultiJvmNode1
[error] Failed: com.lightbend.lagom.scaladsl.persistence.cassandra.CassandraClusteredPersistentEntitySpecMultiJvmNode2
[error] Failed: com.lightbend.lagom.scaladsl.persistence.cassandra.CassandraClusteredPersistentEntitySpecMultiJvmNode3

Issue Analytics

State:
Created 7 years ago
Comments:22 (22 by maintainers)

Top GitHub Comments

2reactions

dwijnandcommented, Jan 8, 2019

Guilty

0reactions

ignasi35commented, Sep 6, 2018

Hmmm, OK. We’ve had quiet periods in the past like this period we’re in (since Jul 23rd). We can close.

Top Results From Across the Web

Spring Data for Apache Cassandra - Reference Documentation

The Spring Data for Apache Cassandra project applies core Spring concepts to the development of solutions using the Cassandra Columnar data ...

Lagom Cassandra defaults could lead to DoS #730 - GitHub

Given a Cassandra cluster killing targeted nodes causes Lagom to experience two sorts of unavailabilities. Scenario 1: killing a particular node ...

Cassandra error: "Clustering key columns must exactly match ...

This is happening because you have only specified a single PRIMARY KEY. Single PRIMARY KEYs default to become partition keys.

Entity testing raising exception trying to connect to Cassandra

I'm using Lagom 1.6.0-M5. I defined an Entity Spec test which uses the PersistentEntityTestDriver which allows to run the test without ...

Cassandra Setup - Lagom Framework

Storing Persistent Events in Cassandra. This page describes how to configure Cassandra for use with Persistent Entity API or Akka Typed Persistence in...