activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-200) activemq-cpp-2.2.1 test fails for decaf::io::ByteArrayInputStreamTest::testConstructor (segmentation fault)
Date Tue, 21 Oct 2008 21:02:52 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46648#action_46648
] 

Timothy Bish commented on AMQCPP-200:
-------------------------------------

I don't think that this is actually a problem with the client code, but instead a bug in the
test.  If you look at the source for that testBasics test in the CMSTemplate integration test
the code uses a Thread::sleep to wait for another thread to be ready before it starts sending,
this is not the best of ideas.  I'd bet that if you run the tests enough times that sleep
would fail to wait long enough and the receiver would not get all the messages its expecting.
 I'll have to look at it closer, I didn't write the CMSTemplate stuff so I need to spend some
time getting familiar with all the internals but at first glance the sleep makes me very suspicious.
 



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


Mime
View raw message