activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Martens (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-199) Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
Date Tue, 07 Oct 2008 16:37:55 GMT

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

Alexander Martens commented on AMQCPP-199:
------------------------------------------

Hello,

Albert, Timothy, since I was getting unit test errors on RHEL5.2, I've switched to a FC8 to
continue stress testing.

This time libactivemq-cpp passes its unit tests.

Stress testing still causes segmentation faults (this time when closing on class destructors)
. You were right, it looks as if ActiveMQ is leaking handles (threads, may be?). I have no
easy way to know if the problem is either on the server side, the client side, the chair-keyboard
interface (probably) or on all of them.

Concerning  the new test environment:

ActiveMQ 5.1.0 (default configuration) and , jre1.6.0_03
FC8, gcc 4.1.2, apr-1.3.3 (unit test passed), apr-utils-1.3.4 (unit test passed), activemq-cpp-2.2.1,
pyactivemq, boost 1_34

See stress-fc8.log.gz for details.


> Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
> ----------------------------------------------------------------
>
>                 Key: AMQCPP-199
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-199
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Decaf, Openwire
>    Affects Versions: 2.2.1
>         Environment: RHEL 5.2 (32 bits), apr-1.3.3, apr-util-1.3.4, ActiveMQ 5.1, gcc
4.1.2-42 (20071124), Java(TM) SE Runtime Environment (build 1.6.0_06-b02), pyactivemq-0.1.0rc1
>            Reporter: Alexander Martens
>            Assignee: Timothy Bish
>         Attachments: stress.out
>
>
> We're getting occasional segmentation faults in our Python based application.
> The easiest way to reproduce it is by running pyactivemq's stress tests (src/tests/stresstest.py).
> The offending line seems to be always the same.
> I send you attached a full gdb postmortem back-trace.
> Any help will be appreciated!

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