Skip to content

NettyResponseFuture can wait indefinitely? #1070

Closed
@jon-ruckwood

Description

@jon-ruckwood

A http request was made days ago, the thread dump indicates that it was waiting - there may have been an unknown issue with the upstream server when the request was in progress:

Foo-1 id=19 state=WAITING
    - waiting on <0x55f017db> (a java.util.concurrent.CountDownLatch$Sync)
    - locked <0x55f017db> (a java.util.concurrent.CountDownLatch$Sync)
    at sun.misc.Unsafe.park(Native Method)
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
    at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
    at com.ning.http.client.providers.netty.future.NettyResponseFuture.get(NettyResponseFuture.java:152)
    ...

Nothing in the logs indicates an error/exception was encountered by async-http-client (logging is set to INFO).

I am using version 1.9.15 and I am creating the client as such:

AsyncHttpClient client = new AsyncHttpClient();

I appreciate there's not much to go on but do you know what may have happened here?

I'm considering using NettyResponseFuture#get(long l, TimeUnit tu) instead but I would have thought that something would have aborted processing given the time involved?

Thanks in advance.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions