[
https://issues.apache.org/activemq/browse/AMQCPP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47244#action_47244
]
Timothy Bish commented on AMQCPP-202:
-------------------------------------
This looks like the same problem as before, threads three and two are both
using the same ActiveMQSessionExecutor. I'm still working my way through the
CMSTemplate code, I have a feeling there is a bug in its Resource management
code that is allowing the same session to get used twice, but not quite sure
how that's happening yet.
I would comment it out for now and see if you can run your tests to completion.
That way if there's any other bugs still hiding we can see them without this
test getting in the way.
> 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.
