4.1.2/3

[383124397]

We use httpasyncclient as our core async RPC component, but we found a recovering issue a couple days ago.
it is the async client will be stoped because of I/O reactor shutdown when a service encounter a OOM problem, a few seconds later and after a FGC process, the service has been recovered, but the async client cannot be recovered. so the client cannot accept the request unless the service need to reboot.

the code is:
@Override public void run() { try { final IOEventDispatch ioEventDispatch = new InternalIODispatch(handler); connmgr.execute(ioEventDispatch); } catch (final Exception ex) { log.error("I/O reactor terminated abnormally", ex); } finally { status.set(Status.STOPPED); } }
or by close() method.
so there is no way to set status from STOPPED to ACTIVE even by start().

[ok2c]

@383124397 Exactly what kind of changes are you proposing? Your pull request looks completely messed up. Please resolve all conflicts and resubmit.

[garydgregory]

@383124397 Please provide your patch on top of the HEAD of the 4.1.x branch. It looks like you are based on code from a 4.1.1-SNAPSHOT. Thank you!

[ok2c]

@383124397 could you please either update the change-set or close this pull request?

[383124397]

I am so sorry that I mark a mistake.