activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQCPP-199) Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
Date Wed, 12 Nov 2008 12:58:05 GMT


Timothy Bish commented on AMQCPP-199:

This one looks more like a normal wait, as in the case where the broker has been exhausted
of resources like we were seeing before.  I assume you aren't restarting the broker here since
the python stress tests run themselves in a loop instead of having a script do it for you.

I ran these last night and it ran fine each time until the broker ran out of memory. 

> 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
>             Fix For: 2.2.2
>         Attachments: python.stress.log.gz, stress-fc8.log.gz, 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