[concurrency-interest] ReentrantLock bug?

Kirk Pepperdine kirk at kodewerk.com
Fri Mar 20 02:04:51 EDT 2015

I see app’s survive OOME because only the offending thread gets shot down. After the request that causes the OOME is shot down, the rest of the app works fine.. for some definition of fine.


On Mar 19, 2015, at 9:52 PM, Dmitry Zaslavsky <dmitry.zaslavsky at gmail.com> wrote:

> I doubt it's one of those conditions.
> I would expect the process to die but it's perfectly fine otherwise. Due to this issue it looks like a deadlocked process
> Sent from mobile device
> On Mar 19, 2015, at 4:50 PM, Vladimir Sitnikov <sitnikov.vladimir at gmail.com> wrote:
>> I typically observe 'invalid' state of ReentrantLock due to StackOverflowError/OutOfMemoryError.
>> Can you try your application with extended stack size and/or check for SOE/OOM?
>> Regards,
>> Vladimir Sitnikov
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20150320/c7364814/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20150320/c7364814/attachment.bin>

More information about the Concurrency-interest mailing list