[jira] [Commented] (QPID-7317) Deadlock on publish

["Brian Bouterse (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346542#comment-15346542 ] 

Brian Bouterse commented on QPID-7317:
--------------------------------------

There is no logging that the background thread is dying. On the EL6 machine the following turned up nothing:     `grep -r Fatal /var/log/`
Also on F23 (journalctl) the following turned up nothing:    journalctl --no-pager -l | grep Fatal

We expect 'Fatal' to be in the logged message because both implementations were verified to contain the logging with this commit [0]. The line we expect to log is here [1]. Per the commit message in [0], I think the thread that is dying is called the Selector thread.

I also grepped for `grep -r "thread has" journalctl_output.txt` thinking it could be logged by this line [2].

[0]: https://github.com/apache/qpid/commit/11368ef1a01233f253eb9eadbadaa9cb9b8465f3
[1]: https://github.com/apache/qpid/blob/trunk/qpid/python/qpid/messaging/driver.py#L420
[2]: https://github.com/apache/qpid/commit/11368ef1a01233f253eb9eadbadaa9cb9b8465f3#diff-a2870153748f29e8583ccdbe0c527e8dR157

> Deadlock on publish
> -------------------
>
>                 Key: QPID-7317
>                 URL: https://issues.apache.org/jira/browse/QPID-7317
>             Project: Qpid
>          Issue Type: Bug
>          Components: Python Client
>    Affects Versions: 0.32
>         Environment: python-qpid-0.32-13.fc23.noarch
>            Reporter: Brian Bouterse
>
> When publishing a task with qpid.messaging it deadlocks and our application cannot continue. This has not been a problem for several releases, but within a few days recently, another Satellite developer and I both experienced the issue on separate machines, different distros. He is using a MRG built pacakge (not sure of version). I am using python-qpid-0.32-13.fc23.
> Both deadlocked machines had core dumps taken on the deadlocked processes and only show only 1 Qpid thread when I expect there to be 2. There are other mongo threads, but those are idle as expected and not related. The traces show our application calling into qpid.messaging to publish a message to the message bus.
> This problem happens intermittently, and in cases where message publish is successful I've verified by core dump that there are the expected 2 threads for Qpid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org