issue with Cassandra in pekko-sample-distributed-workers-scala
- Dominant language
- Scala
- Stars
- 74
- Forks
- 35
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 4
Description
On a stable Debian (OpenJDK 17), the example pekko-sample-distributed-workers-scala will fail on a exception while using `sbt run` or `sbt "runMain worker.Main cassandra"`.
The logs
```txt
Starting Cassandra on port client port: 9042 storage port 45209 host 127.0.0.1 java version 17.0.10+7-Debian-1deb12u1
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.apache.cassandra.security.ThreadAwareSecurityManager (file …/pekko-samples/pekko-sample-distributed-workers-scala/target/cassandra-db/cassandra-bundle.jar)
WARNING: Please consider reporting this to the maintainers of org.apache.cassandra.security.ThreadAwareSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
Exception (java.lang.AssertionError) encountered during startup: java.lang.reflect.InaccessibleObjectException: Unable to make field private int java.io.FileDescriptor.fd accessible: module java.base does not "opens java.io" to unnamed module @11b03c1f
java.lang.AssertionError: java.lang.reflect.InaccessibleObjectException: Unable to make field private int java.io.FileDescriptor.fd accessible: module java.base does not "opens java.io" to unnamed module @11b03c1f
…
[error] at worker.Main$.startCassandraDatabase(Main.scala:101)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with worker.Main.startCassandraDatabase at Main.scala:101 and reproduce the failure using sbt run or sbt "runMain worker.Main cassandra" on Debian with OpenJDK 17. Check how the bundled Cassandra process starts and identify the cause of the InaccessibleObjectException; done means the sample starts Cassandra successfully without this startup exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, debian, java, scala
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100