You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create an instance of PushAsyncService, it automatically creates an AsyncHttpClient instance upon initialization. The client spawns some threads that prevent my whole application from shutting down (e.g. if a fatal configuration error was encountered).
If there was a close() or stop() method to call I would do so, but there is none and httpClient is private so I cannot access it (at least without resorting to reflection). If I "cheat" and call close() on the private httpClient, the app proceeds to shut down normally.
The text was updated successfully, but these errors were encountered:
When I create an instance of
PushAsyncService
, it automatically creates anAsyncHttpClient
instance upon initialization. The client spawns some threads that prevent my whole application from shutting down (e.g. if a fatal configuration error was encountered).If there was a
close()
orstop()
method to call I would do so, but there is none andhttpClient
is private so I cannot access it (at least without resorting to reflection). If I "cheat" and callclose()
on the privatehttpClient
, the app proceeds to shut down normally.The text was updated successfully, but these errors were encountered: