[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47011#action_47011
]
Timothy Bish commented on AMQCPP-200:
-------------------------------------
While we've reduced the load by turning off persistence for as many tests as we
can, some require it. Also there the fact that we create a large number of
topics and queues on each run that are not deleted yet since we don't yet have
that feature. If you connect to the broker via JMX after about 30 runs of the
client integration tests without restarting the broker you will see a huge list
of them. Assuming that the JVM heap space hasn't been set to some huge number
I'd expect that eventually we would just exhaust the available resources that
the broker has access to.
Someday we will be able to clean up the mess on the broker at then end of each
test, but for now we can't.
> 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.
