Alexander Kolesnikov
Alexander Kolesnikov
Also reproduced on Jetty 10.0.10, but cannot reproduce on 10.0.9
@joakime Logback 1.2.* is not abandoned and in fact is being developing in parallel with 1.3.* Migration to the latest version is not an option right now due to dependencies...
> The lock created by com.workato.agent.log.CloudAppender seems to be the cause, not the lock in AdaptiveExecutionStrategy (at least that's what we can tell from your limited stacktrace) This class doesn't...
@sbordet A servlet container as a universal tool is expected to be able to correctly work in different environments. In this scenario, one of the critical classes from Jetty internals...
@sbordet Of course, it can be reproduced with the Logback library only. But the same is true for the opposite: we have been using this logger for years and never...
> File an issue there, or change the buggy library you are using. That's why this issue was created. Both Jetty and Logback have the same bug - they call...
> And we are not calling alien methods. We are calling a logging API (SLF4J) that you have bound to a buggy implementation. Change the logging implementation and your problems...
@cla-bot check
@chernser > Regarding Object[] for each row. This is done because of safety considerations: when value holder is reused then potentially a wrong data can be read from previous row....