[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46888#action_46888
]
Timothy Bish commented on AMQCPP-200:
-------------------------------------
Looking at the logs it now appears like the code isn't shutting down, but
instead waiting because the receiver hasn't received the number of messages
that its been told it should have. What I think is happening is that the CMS
template code is sending message persistently by default, and we can't purge
the queues on exit in our tests yet so you are running out of space on the
broker.
I'm betting that if we sent the messages with non persistent messaging we
wouldn't see this problem. You can add
cmsTemplate.setDeliveryPersistent(false) to the constructors of the sender and
receiver class in the file:
/activemq-trunk-cpp/src/test-integration/integration/connector/openwire/OpenwireCmsTemplateTest.h
I will try this later on to see, but I think I just wasn't running my tests
through enough iterations with the broker config that I currently have.
> 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.7.log.gz, deadlock.8.log.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.
