[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-200:
-------------------------------------
Attachment: daemons.1.tar.gz
Wow.
Your latest comment has open hell's doors and a couple of daemons came out,...
(listening to Haggard on my mp3)
I've commented everything but the CmsTemplate test and added the
persistent=false at the "broker" element in my activemq.xml.
Got one segmentation fault. I changed long_run to include a "ulimit -c
unlimited" and got one segmentation fault (again) and a few iterations after, a
lock.
I send you attached the output, my new activemq.xml, and postmortems for the
dumped core and the running deadlock.
Best of all is that I don't need too much time to reproduce it. Is fast!
Hope this helps.
BTW: Segfault becasue of
Program terminated with signal 11, Segmentation fault.
#0 0x001ce5b4 in run_cleanups (cref=0x9fafcf0) at memory/unix/apr_pools.c:2306
2306 (*c->plain_cleanup_fn)((void *)c->data);
* 1 process 3620 0x001ce5b4 in run_cleanups (cref=0x9fafcf0) at
memory/unix/apr_pools.c:2306
> 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,
> 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.
