[
https://issues.apache.org/activemq/browse/AMQCPP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47286#action_47286
]
Alexander Martens commented on AMQCPP-202:
------------------------------------------
Morning!
The night test is still running (on #657 now) (without CMSTemplate) !!
I'll let it a few hours more to be sure that the problem relies on this
particular test; btw, there were no segmentation faults either.
On the other hand, AMQCPP-199 stopped on the 75th pass - I'll connect gdb now
to see what's going on there, and post the log file at AMQCPP-199.
For the double thread, I'll have to take a deeper look at the code to figure
out a way to detect it and break the execution.
BTW, which APR version are you running? We should be seeing the same locks...
> 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.
