[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46862#action_46862
]
Timothy Bish commented on AMQCPP-200:
-------------------------------------
This appears to be a deadlock issue on close down. I can't reproduce it here,
I've let this test run for hours. How are you running your tests, using a
script to continuously start the integration tests, or by modifying the test's
main method?
I can't see from the log file what the other threads are doing, it would be
nice to figure out who is holding the lock that is causing the deadlock. I'll
keep trying.
> activemq-cpp-2.2.1 test fails for
> decaf::io::ByteArrayInputStreamTest::testConstructor (segmentation fault)
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-200
> URL: https://issues.apache.org/activemq/browse/AMQCPP-200
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Decaf
> Affects Versions: 2.2.1
> Environment: RHEL 5.2 (2.6.18-92.el5), apr-1.3.3, apr-util-1.3.4,
> cppunit-1.12.1, gcc version 4.1.2 20071124 (Red Hat 4.1.2-42), Java(TM) SE
> Runtime Environment (build 1.6.0_06-b02)
> Reporter: Alexander Martens
> Assignee: Timothy Bish
> Fix For: 2.2.2
>
> Attachments: CentOS-AprPool-Fix-Test.patch, deadlock.6.tar.gz,
> deadlock.log.gz, deadlock.openwire.join.tar.gz, deadlock2.log.gz,
> openwire_transaction.tar.gz, seg_fault.log.gz, setup.tar.gz,
> testConstructor-O0.log.gz, testConstructor.log.gz, testString-O0.log.gz
>
>
> This unit test seems to fail.
> I send you attached a gdb postmortem log (bt, bt full, info threads).
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
