I am using SLF4J for logging in a multithreaded application. In one instance, I am interrupting a Thread (using
Thread.interrupt()). When this Thread is then using SLF4J to log an error, I receive the following exception from the APM agent (version 1.31.0):
ERROR co.elastic.apm.agent.bci.IndyBoostrap - null
It would be great if the APM agent could handle this scenario without this Exception.
Is there a functional/observational issue here, or is the desire only for the stack trace to not be emitted?
Good question. My first assumption was that a log entry of type ERROR by the ElasticAPM agent appertaining on the console would indicate that something is wrong with the agent.
I haven’t observing any issues with the functionality, although I cannot tell for sure if the error has any side-effects or not.
So your take would be that this error can simply be ignored in this case?
Does it continue happening, or just the first time after the interrupt? I think the former would mean the logger doesn't get bytecode transformed, whereas the latter would just lose the odd error from apm
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.