activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Martens (JIRA)" <>
Subject [jira] Updated: (AMQCPP-199) Segmentation fault at decaf/net/SocketInputStream.cpp (line 108)
Date Tue, 18 Nov 2008 07:57:05 GMT


Alexander Martens updated AMQCPP-199:

    Attachment: stress-waits.tar.gz

Albert, Timothy

It blocked again, even with a server restart every 50 loops - it completed the cycle twice
and went stranded around loop 39.

I'm looking forward to close this issue as its subject wasn't reproduce after the changes
made during the past weeks, but the point is that I cannot keep the stress test for too long
(less than a couple of hours).

What I've also noticed is that it seems to block at the same test (test_openwire_async), so
I'm giving it another try without it, like we did with the CMSTemplate.

Anyway, it would be ok to me to close this thread if you agree that the log files attached
have little or nothing to do with the original segmentation fault that opened this issue.

> 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-again.tar.gz, stress-fc8.log.gz, stress-segfault-1.log.bz2,
stress-waits.tar.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