activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQCPP-464) Deadlock during normal task termination
Date Mon, 18 Feb 2013 23:41:13 GMT


Timothy Bish commented on AMQCPP-464:

Currently on line 458 (setHead) of AbstractQueuedSynchronizer.cpp we set the thread pointer
to NULL, don't really need to but we do.  You can comment that out and then you'll see who
currently owns the lock during this deadlock.  The second thread is at waitStatus = -1 meaning
its waiting to be signaled that the thread holding the lock is done, and the third on is zero
for reason I can't remember right now but should be fine since its second in line to get the
> Deadlock during normal task termination
> ---------------------------------------
>                 Key: AMQCPP-464
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Decaf
>    Affects Versions: 3.6.0
>         Environment: Windows XP VS2005
>            Reporter: Scott Weaver
>            Assignee: Timothy Bish
>            Priority: Critical
>         Attachments: CrashHang_Report__CMStressD.exe__02182013132527878.mht
> Normal task termination hangs occasionally.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message