Closed kcris closed 7 years ago
I'm pretty sure that this is your issue: https://github.com/kamon-io/sigar-loader/tree/master/core/src/main/resources#provision-from-several-jvm
Please ensure that each JVM gets its own folder for unpacking the sigar native binaries and all should be good!
thanks a lot! I now pass
-javaagent:../lib/sigar-loader-1.6.5-rev002.jar=kamon.sigar.folder=../tmp/sigar/x
to jvm, but I get a warning, kamon-akka and kamon-scala complain that they still want aspectj as javaagent (I used aspectj previously, I just switched now to sigar-loader due to my issue)
It seems like your application was not started with the -javaagent:/path-to-aspectj-weaver.jar option but Kamon detected
the following modules which require AspectJ to work properly:
kamon-akka, kamon-scala
what is the right way to deal with this?
thanks a lot Chris
Just ensure that your application is started with the -javaagent:/path-to-aspectjweaver.jar
option and that's it, that's for the instrumentation provided by kamon-scala and kamon-akka to work properly.
so, I guess I have to pass both as javaagents -aspectj -sigar-loader (pointed by your link above), which allows customizing the kamon.sigar.folder
thanks a lot
Hi, I have a scala (2.11.7) app that runs on linux and uses akka (2.4.14) + kamon (0.6.3). One instance runs fine, kamon is happy and all.
As soon as I start the second instance with kamon enabled, the jvm crashes. The java vm itself is aborted with a core dump (not my application). Any number of instances other than 1, results in the same behavior.
The same app without kamon, runs perfectly with many instances on linux. Also, tried multiple instances on Windows, I get no crash with kamon enabled.
The generated log shows indeed this has something to do with kamon.
See below the os/environment details
crash log
Thanks Chris