activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Strasheim (JIRA)" <>
Subject [jira] Commented: (AMQCPP-199) Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
Date Sun, 05 Oct 2008 20:18:52 GMT


Albert Strasheim commented on AMQCPP-199:


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?



> Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
> ----------------------------------------------------------------
>                 Key: AMQCPP-199
>                 URL:
>             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/
> 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.

View raw message