[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46999#action_46999
]
Timothy Bish commented on AMQCPP-200:
-------------------------------------
Alexander
Just wanted to confirm, are you stopping and starting the broker between each
run of the integration tests? I ran several continuous runs this weekend with
my script that starts and stops a broker and haven't been able to cause the
deadlock that you are seeing. From the logs I've seen, the deadlocks all look
like the client just didn't receive the expected message from the broker and is
stopped waiting.
We should probably make them timed receives with long timeouts so that the
tests will eventually fail. I will look into that later on today. I did fix a
few memory leaks, some in the lib code, most in the unit tests over the
weekend, I am continuing to try and get a clean valgrind run of the unit tests
just to make sure we aren't losing any resources anywhere.
> 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, daemons.1.tar.gz,
> deadlock.6.tar.gz, deadlock.7.log.gz, deadlock.8.log.gz, deadlock.9.tar.gz,
> deadlock.log.gz, deadlock.openwire.join.tar.gz, deadlock2.log.gz,
> more.daemons.tar.gz, openwire_transaction.tar.gz, quota.2.tar.gz,
> seg_fault.log.gz, setup.tar.gz, storage_logs.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.
