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.

Tests launch Cassandra with debug logging enabled

See original GitHub issue

Lagom Version (1.2.x / 1.3.x / etc)

1.3.6

API (Scala / Java / Neither / Both)

Java

Reproducible Test Case

sbt new lagom/lagom-java.g8 --lagom_version=1.3.6
cd hello
sbt test

Note the extremely verbose output.

I don’t see this when creating a new project from the Scala g8 template or the Java Maven archetype.

Issue Analytics

State:
Created 6 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

TimMoorecommented, Aug 10, 2017

I worked out why this only happens with the Java g8 template, and not with the Scala one: lagom/lagom-java.g8 is the only one that doesn’t include a default logback.xml or logback-test.xml in the test resources directory. This is picked up off the classpath when launching Cassandra in Lagom 1.3.x.

In 1.4.x, the Cassandra bundle used by the launcher includes its own logback.xml.

So, I think the expedient solution will be to add one to the Java archetype as well. I think it’s good to have config file scaffolding, anyway, so you can make changes without having to copy it in from the docs.

0reactions

TimMoorecommented, Aug 10, 2017

Moved to https://github.com/lagom/lagom-java.g8/issues/19

Top Results From Across the Web

Configuring logging | Apache Cassandra 3.0

Logs are written to the system.log and debug.login the Cassandra logging directory. You can configure logging programmatically or manually.

Cassandra Logs | Apache Cassandra Documentation

Cassandra has three main logs, the system.log , debug.log and gc.log which hold general logging messages, debugging logging messages, and java garbage ...

commons-logging to debug in Cassandra - Stack Overflow

I'm working on the code of Cassandra 2.2. EDIT: Using the solution below, I got the following output right after starting the debugger:...

cassandra-dtest/run_dtests.py at trunk - GitHub

--dtest-enable-debug-logging Enable debug logging (for this script, pytest, and during execution of test functions) (default: False).

The Basics of Monitoring Cassandra | Logging - InformIT

Now your Cassandra node will be running in DEBUG mode. To change it back, just swap the INFO and DEBUG again. To show...