You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Albert Strasheim (JIRA)" <ji...@apache.org> on 2008/10/05 22:18:52 UTC
[jira] Commented: (AMQCPP-199) Segmentation fault at
decaf/net/SocketInputStream.cpp (line 108)
[ https://issues.apache.org/activemq/browse/AMQCPP-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46182#action_46182 ]
Albert Strasheim commented on AMQCPP-199:
-----------------------------------------
Hello,
I've also seen a segfault once while running the pyactivemq stress tests, which was caused by the broker (AMQ 5.1.0) running out of memory for some unknown reason.
I'll see if I can reproduce this issue on my side, but it would be useful to know if it always happens with a specific part of the stress test?
Cheers,
Albert
> 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.