That did the trick! Thanks. I also recognized that one down in the
contribution.md
I guess it would be also a good idea to show this notice if jolokia fails
to attach.
Thanks guys!
2016-10-06 14:12 GMT+02:00 Marcus Eriksson :
> It is this: "-XX:+PerfDisableSharedMem" - in your dtest you need to
It is this: "-XX:+PerfDisableSharedMem" - in your dtest you need to do
"remove_perf_disable_shared_mem(node1)" before starting the node
/Marcus
On Thu, Oct 6, 2016 at 8:30 AM, Benjamin Roth
wrote:
> Maybe additional information, this is the CS command line for ccm node1:
>
> br 20376 3.2
I had this problem before but can't remember the root cause, but I think it
was related to conflicting JVMs on the same machine. Can you check if you
have more than one JVM installed and try to define JAVA_HOME if it's not
defined?
Maybe this is related: https://github.com/rhuss/jolokia/issues/189
Maybe additional information, this is the CS command line for ccm node1:
br 20376 3.2 8.6 2331136 708308 pts/5 Sl 06:10 0:30 java
-Xloggc:/home/br/.ccm/test/node1/logs/gc.log -ea -XX:+UseThreadPriorities
-XX:ThreadPriorityPolicy=42 -XX:+HeapDumpOnOutOfMemoryError -Xss256k
-XX:StringTa
Since some days I have the problem that I cannot run a dtest as jolokia
fails to attach to the process.
It worked some days ago. I tried both on MacOS + Linux with dtest master
and pip'ed requirements.
dtest output is:
Failed to start jolokia agent (command was:
/usr/lib/jvm/oracle-java8-jdk-amd64
