[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46613#action_46613
]
Timothy Bish commented on AMQCPP-200:
-------------------------------------
The deadlock logs look like its stuck in a send. Currently the most common
reason for a send to stall is that we are being producer flow controlled. Are
you connecting to a broker that is in use by anyone else? Is this broker local
to the machine you are on or in your control? If so can you change the
configuration to disable flow control and run some more tests to see if these
stalls repeat?
I've had occasional failures on those stomp tests but they are so infrequent
that I've never been able to determine if its the stomp code or the tests that
are at fault. I'd ignore stomp issues for the moment unless you are planning
on using the stomp protocol which I don't recommend as the openwire protocol
performs better and offers a more complete set of features.
> 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.log.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.
