[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-200:
-------------------------------------
Attachment: deadlock.7.log.gz
Sorry for the late answer, it has been a busy day.
Here you're. 20 threads, some reading, some waiting for a condion,...
I've dumped the standard backtrace for each one hoping this is enough for you
get a light bulb over your head. If not, the process is stopped in a dedicated
server for this issue, so that I can attach gdb and inspect any variable in any
thread, any time. Just drop me a mail or post a message.
Hope this helps!
> 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.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.
