activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Martens (JIRA)" <>
Subject [jira] Commented: (AMQCPP-200) activemq-cpp-2.2.1 test fails for decaf::io::ByteArrayInputStreamTest::testConstructor (segmentation fault)
Date Wed, 29 Oct 2008 19:27:54 GMT


Alexander Martens commented on AMQCPP-200:


Your explanation sounds pretty reasonable to me. If so, this long test is the good one (crossing
fingers) - I better go home (is quite late here) and have some dinenr.
(I was wondering... if server quotas are fixed - I didn't change the activemq.xml - as well
as the number of messages sent by the test, shouldn't we seeing a stop at the same iteration
#, given that my scripts to start and stop activemq - that I'm running at the beginning of
each long run - are recursively deleting ActiveMQ's data directory? Hmmm.
Never mind. We'll see thta tomorrow.)

I know I've said this many times, but thanks a lot Timothy.

> activemq-cpp-2.2.1 test fails for decaf::io::ByteArrayInputStreamTest::testConstructor
(segmentation fault)
> -----------------------------------------------------------------------------------------------------------
>                 Key: AMQCPP-200
>                 URL:
>             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.

View raw message