Deadlock
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- backend, observability-sre
Línea de trabajo
Parte de los stack traces proporcionados, especialmente logback's AppenderBase.doAppend y Jetty's AdaptiveExecutionStrategy.toString, y reproduce el deadlock mientras experimentas con filtros. Rastrea el ciclo de bloqueo entre el appender y la estrategia de ejecución de Jetty; se considera terminado cuando la REPL y el servidor web local ya no se quedan bloqueados.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I hit this deadlock while using cider-log-mode. I'm using logback-classic. This let the repl and local websever stuck indefinitely.
Last thing I was trying to do is to play with the filters.
These are the two stacktraces (separated by waiting to lock lines)
Stacks
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Name |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| +---qtp2043949759-134 Blocked waiting to lock logjam.framework.logback.proxy$ch.qos.logback.core.AppenderBase$ff19274a@5a5c59ee which is held by qtp2043949759-139 |
| | | |
| | +---ch.qos.logback.core.AppenderBase.doAppend AppenderBase.java:64 |
| | | |
| | +---logjam.framework.logback.proxy$ch.qos.logback.core.AppenderBase$ff19274a.doAppend |
| | | |
| | +---ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders AppenderAttachableImpl.java:51 |
| | | |
| | +---ch.qos.logback.classic.Logger.appendLoopOnAppenders Logger.java:272 |
| | | |
| | +---ch.qos.logback.classic.Logger.callAppenders Logger.java:259 |
| | | |
| | +---ch.qos.logback.classic.Logger.buildLoggingEventAndAppend Logger.java:426 |
| | | |
| | +---ch.qos.logback.classic.Logger.filterAndLog_2 Logger.java:419 |
| | | |
| | +---ch.qos.logback.classic.Logger.debug Logger.java:495 |
| | | |
| | +---org.eclipse.jetty.util.thread.ReservedThreadExecutor.startReservedThread ReservedThreadExecutor.java:256 |
| | | |
| | +---org.eclipse.jetty.util.thread.ReservedThreadExecutor.tryExecute ReservedThreadExecutor.java:236 |
| | | |
| | +---org.eclipse.jetty.util.thread.QueuedThreadPool.tryExecute QueuedThreadPool.java:809 |
| | | |
| | +---org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.selectSubStrategy AdaptiveExecutionStrategy.java:340 |
| | | |
| | +---org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce AdaptiveExecutionStrategy.java:277 |
| | | |
| | +---org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.produce AdaptiveExecutionStrategy.java:193 |
| | | |
| | +---org.eclipse.jetty.io.ManagedSelector$$Lambda/0x0000000803dee978.run |
| | | |
| | +---org.eclipse.jetty.util.thread.QueuedThreadPool.runJob QueuedThreadPool.java:969 |
| | | |
| | +---org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob QueuedThreadPool.java:1194 |
| | | |
| | +---org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run QueuedThreadPool.java:1149 |
| | | |
| | +---java.lang.Thread.runWith Thread.java:1596 |
| | | |
| | +---java.lang.Thread.run Thread.java:1583 |
| | |
| +---qtp2043949759-139 Waiting waiting to lock java.util.concurrent.locks.ReentrantLock$NonfairSync@6d05fd22 which is held by qtp2043949759-134 |
| | |
| +---jdk.internal.misc.Unsafe.park Unsafe.java (native) |
| | |
| +---java.util.concurrent.locks.LockSupport.park LockSupport.java:221 |
| | |
| +---java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire AbstractQueuedSynchronizer.java:754 |
| | |
| +---java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire AbstractQueuedSynchronizer.java:990 |
| | |
| +---java.util.concurrent.locks.ReentrantLock$Sync.lock ReentrantLock.java:153 |
| | |
| +---java.util.concurrent.locks.ReentrantLock.lock ReentrantLock.java:322 |
| | |
| +---org.eclipse.jetty.util.thread.AutoLock.lock AutoLock.java:44 |
| | |
| +---org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.toString AdaptiveExecutionStrategy.java:542 |
| | |
| +---org.slf4j.helpers.MessageFormatter.safeObjectAppend MessageFormatter.java:291 |
| | |
| +---org.slf4j.helpers.MessageFormatter.deeplyAppendParameter MessageFormatter.java:263 |
| | |
| +---org.slf4j.helpers.MessageFormatter.arrayFormat MessageFormatter.java:225 |
| | |
| +---org.slf4j.helpers.MessageFormatter.arrayFormat MessageFormatter.java:160 |
| | |
| +---ch.qos.logback.classic.spi.LoggingEvent.getFormattedMessage LoggingEvent.java:396 |
| | |
| +---logjam.framework.logback$event_data.invokeStatic logback.clj:58 |
| | |
| +---logjam.framework.logback$event_data.invoke logback.clj:51 |
| | |
| +---logjam.framework.logback$add_appender$fn__1486127.invoke logback.clj:68 |
| | |
| +---logjam.framework.logback.proxy$ch.qos.logback.core.AppenderBase$ff19274a.append |
| | |
| +---ch.qos.logback.core.AppenderBase.doAppend AppenderBase.java:83 |
| | |
| +---logjam.framework.logback.proxy$ch.qos.logback.core.AppenderBase$ff19274a.doAppend |
| | |
| +---ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders AppenderAttachableImpl.java:51 |
| | |
| +---ch.qos.logback.classic.Logger.appendLoopOnAppenders Logger.java:272 |
| | |
| +---ch.qos.logback.classic.Logger.callAppenders Logger.java:259 |
| | |
| +---ch.qos.logback.classic.Logger.buildLoggingEventAndAppend Logger.java:426 |
| | |
| +---ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus Logger.java:386 |
| | |
| +---ch.qos.logback.classic.Logger.debug Logger.java:499 |
| | |
| +---org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.reservedWait ReservedThreadExecutor.java:327 |
| | |
| +---org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run ReservedThreadExecutor.java:401 |
| | |
| +---org.eclipse.jetty.util.thread.QueuedThreadPool.runJob QueuedThreadPool.java:969 |
| | |
| +---org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob QueuedThreadPool.java:1194 |
| | |
| +---org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run QueuedThreadPool.java:1149 |
| | |
| +---java.lang.Thread.runWith Thread.java:1596 |
| | |
| +---java.lang.Thread.run Thread.java:1583 |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Generated by YourKit Java Profiler 2023.9-b101 January 12, 2024 07:59:24 AM
I'm using:
- ch.qos.logback/logback-classic 1.4.14
- org.slf4j/slf4j-api 2.0.10
- org.clojure/tools.logging 1.2.4
- org.eclipse.jetty/jetty-server 11.0.18
- Lenguaje dominante
- Clojure
- Estrellas
- 2
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de clojure-emacs/logjam
-
Record file/ns/line/col infoAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
clojure-emacs/logjam#11 ·
-
Record a friendly timestampAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
clojure-emacs/logjam#9 ·
-
Test in a production-like serverAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
clojure-emacs/logjam#5 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
clojure-emacs/logjam#4 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
clojure-emacs/logjam#3 ·
Todos los issues de clojure-emacs/logjam
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
clojure-emacs/cider#4235 ·
Los mantenedores suelen responder en 1 día
-
needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
`batch-transact-with-temp-conn!` leaves `:max-tx` behind its datoms, so the next transaction reuses a tx idPosiblemente ocupada @tiensonqin la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Server logs every websocket send at DEBUG since #8844, adding lag under loadPosiblemente ocupada @matthewlehew la tomó hace 1 día. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
.Team/Graphy
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
metabase/metabase#87741 · 1 comentario ·
Los mantenedores suelen responder en 1 día