[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46910#action_46910
]
tabish121 edited comment on AMQCPP-200 at 10/30/08 3:29 AM:
---------------------------------------------------------------
Another thing to try is to go to the integration tests TestRegistry.cpp and
comment out everything but the CMS Template test and then run your long test,
this will eliminate the other tests which I know are not all leaving the broker
in a completely clean state on exit. I went through and set some more to use
non persistent messaging last night. Until I get a chance to implement the
delete destinations from the broker on exit by there probably will always be a
bit of sludge left from running these tests.
You can turn off persistence at the broker end:
http://activemq.apache.org/how-do-i-disable-persistence.html
was (Author: tabish121):
Another thing to try is to go to the integration tests TestRegistry.cpp and
comment out everything but the CMS Template test and then run your long test,
this will eliminate the other tests which I know are not all leaving the broker
in a completely clean state on exit. I went through and set some more to use
non persistent messaging last night. Until I get a chance to implement the
delete destinations from the broker on exit by there probably will always be a
bit of sludge left from running these tests.
You can turn off persistence at the broker end:
> 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.9.tar.gz, deadlock.log.gz,
> deadlock.openwire.join.tar.gz, deadlock2.log.gz, openwire_transaction.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.
