GitHub user 383124397 opened a pull request:
https://github.com/apache/httpasyncclient/pull/6
4.1.2/3
We use httpasyncclient as our core async RPC component, but we found a
recover issue a couple days ago.
the issue is the async client will be stoped because of I/O reactor
Github user 383124397 closed the pull request at:
https://github.com/apache/httpasyncclient/pull/7
---
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
Github user 383124397 commented on the issue:
https://github.com/apache/httpasyncclient/pull/7
@ok2c OK
---
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h
Github user 383124397 commented on the issue:
https://github.com/apache/httpasyncclient/pull/6
I am so sorry that I mark a mistake.
---
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands
Github user 383124397 closed the pull request at:
https://github.com/apache/httpasyncclient/pull/6
---
-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
GitHub user 383124397 opened a pull request:
https://github.com/apache/httpasyncclient/pull/7
fix a STOPPED to ACTIVE issue by start method
We use httpasyncclient as our core async RPC component, but we found a
recovering issue a couple days ago.
it is the async client
Github user 383124397 commented on the issue:
https://github.com/apache/httpasyncclient/pull/7
@ok2c I mean there is no way to recover a stopped client if it was shut by
a accident exception like seconds
OOM unless the user renew one. but as a user I don't wanna renew
Github user 383124397 commented on the issue:
https://github.com/apache/httpasyncclient/pull/7
@ok2c I mean it's is good enough if the HttpAsyncClient can support be
recovered from an exception scenario by invoke start method
Github user 383124397 commented on the issue:
https://github.com/apache/httpasyncclient/pull/7
@ok2c so the asynchttpclient is a one-off component for users, I hope it
could be resiliently, high availability... and you know it could be caused
memory leak if we create new client
