[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-200:
-------------------------------------
Attachment: storage_logs.tar.gz
Hi!
It is said that devil is hidden in details:
Following the output log, iteration #57 started on oct 29 21:39:34 GMT 2008.
On the server side (no, there are no errors nor warnings, but there is one
suspicious INFO line, more than one hour later than its previous trace, and
only five minutes before #57):
2008-10-29 21:39:29,738 [127.0.0.1:32874] INFO KahaStore - Kaha Store using
data directory /usr/local/apache-activemq-5.1.0/data/localhost/tmp_storage
du -h -s /usr/local/apache-activemq-5.1.0/data/localhost/tmp_storage says 50M
(a default maximum value?)
However, if the problem is on the server side (because a resource quota leads
it to discard messages, which could be the reason as you pointed out that
pushes the client to an endless wait), a client restart (killing the
integration test only) should stop on the early loops, shouldn't it?
I'm going to test that...
> 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.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.
