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 Sun, 19 Oct 2008 21:47:52 GMT


Alexander Martens commented on AMQCPP-200:

I've been running the integration tests and I've seen weird things on both, ActiveMQ 5.1 and
5.3 (snapshot).
I don't find a common pattern nor a deterministic way to reproduce a problem, though issues
come pretty easily up.
I'm seeing deadlocks (integration::connector::openwire::OpenwireTransactionTest::test), cms
exceptions (StompConnectionNegotiator::requestConnection Negotiate timeout: peer did not send
a connected command) even java crashes (I can post the logs, if you want to have a look at

Furthermore, I even got the tests to pass without problems from time to time.

Concerning the unit-tests (src/test/activemq-test), I've run them about a 100 consecutive
times without problems. I'll let them run a few hundreds more. just to be sure.

(It's  close to midnight here, time for me to have some sleep.)

> 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, 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