Le 04/03/16 21:10, Chris Pike a écrit : > Some more information.... > > I setup my service to periodically print the admin pools active and idle > connections. The hang problem happens after a successful redeploy, but the > web server stops processing requests and the log generally shows 16 active > connections. Is there a timeout check for active connections? I did notice it > is using an old (1.6) version of commons pool, any reason this hasn't been > upgraded?
Ooops... I think we run a check for new version before every release, but I do think they changed the packages, so 1.6 seems to be the latest version. We can easily upgrade to 2.4.2.
