[
https://issues.apache.org/activemq/browse/AMQCPP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47251#action_47251
]
Timothy Bish commented on AMQCPP-202:
-------------------------------------
This is really confusing, I've been through most of the CmsTemplate code and
don't yet see how those two threads could ever come to be. I've run the
CmsTemplate testBasics by itself quite a bit with printouts in various places
but haven't been able to find any instance where this happens. What we need to
find out is where threads two and three get created, that would help to see how
this is happening.
> Occasional Deadlocks when Integration tests are run in a long loop on CentOS
> and REHL.
> --------------------------------------------------------------------------------------
>
> Key: AMQCPP-202
> URL: https://issues.apache.org/activemq/browse/AMQCPP-202
> Project: ActiveMQ C++ Client
> Issue Type: Sub-task
> Components: Integration Tests
> Affects Versions: 2.2.1
> Environment: CentOS and REHL so far.
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 2.2.2
>
> Attachments: locked.again.log.gz, receiving.187.log.gz
>
>
> When run in a continuous loop the integration tests have been seen to
> deadlock.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
