Git Product home page Git Product logo

Comments (2)

cburroughs avatar cburroughs commented on May 17, 2024

Another similar looking one

Java-level deadlocks have been detected

This means that some threads are blocked waiting to enter a synchronization block or
waiting to reenter a synchronization block after an Object.wait() call, where each thread
owns one monitor while trying to obtain another monitor already held by another thread.

Deadlock:


AsyncHttpClient-Reaper is waiting to lock com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture@4dab2dfd which is held by AsyncHttpClient-Reaper
AsyncHttpClient-Reaper is waiting to lock com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture@364e4213 which is held by AsyncHttpClient-Reaper



Deadlock:


AsyncHttpClient-Reaper is waiting to lock com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture@364e4213 which is held by AsyncHttpClient-Reaper
AsyncHttpClient-Reaper is waiting to lock com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture@4dab2dfd which is held by AsyncHttpClient-Reaper




Thread stacks


AsyncHttpClient-Reaper [BLOCKED; waiting to lock com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture@4dab2dfd]
com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.cancel(NettyAsyncHttpProvider.java:1715)
com.ning.http.client.providers.netty.NettyResponseFuture.cancelReaper(NettyResponseFuture.java:196)
com.ning.http.client.providers.netty.NettyResponseFuture.abort(NettyResponseFuture.java:293)
com.ning.http.client.providers.netty.NettyAsyncHttpProvider.abort(NettyAsyncHttpProvider.java:1289)
com.ning.http.client.providers.netty.NettyAsyncHttpProvider.access$700(NettyAsyncHttpProvider.java:136)
com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.run(NettyAsyncHttpProvider.java:1767)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
java.lang.Thread.run(Thread.java:662)


AsyncHttpClient-Reaper [BLOCKED; waiting to lock com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture@364e4213]
com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.cancel(NettyAsyncHttpProvider.java:1715)
com.ning.http.client.providers.netty.NettyResponseFuture.cancelReaper(NettyResponseFuture.java:196)
com.ning.http.client.providers.netty.NettyResponseFuture.abort(NettyResponseFuture.java:293)
com.ning.http.client.providers.netty.NettyAsyncHttpProvider.abort(NettyAsyncHttpProvider.java:1289)
com.ning.http.client.providers.netty.NettyAsyncHttpProvider.access$700(NettyAsyncHttpProvider.java:136)
com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.run(NettyAsyncHttpProvider.java:1767)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
java.lang.Thread.run(Thread.java:662)

from async-http-client.

jfarcand avatar jfarcand commented on May 17, 2024

Fixed, let me know if you can still reproduce.

from async-http-client.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.