Message7637
I see. :)
Yes, this issue still happens with 2.5.2. 1660 was closed in 2010, yet this bug still clearly existed in 2011 when I commented on 1660. I wasn't sure if this defect was a new one (a regression introduced after 1660 was fixed), or if 1660 was never actually fixed (the fix was defective itself).
But this thread consumption still occurs, and with JConsole is easy to see. I've had to write my own thread code to get around this. |
|
Date |
User |
Action |
Args |
2013-02-07 14:42:40 | treaves | set | messageid: <1360248160.92.0.0615198910355.issue1761@psf.upfronthosting.co.za> |
2013-02-07 14:42:40 | treaves | set | recipients:
+ treaves, amak, crankycoder |
2013-02-07 14:42:40 | treaves | link | issue1761 messages |
2013-02-07 14:42:40 | treaves | create | |
|