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 Thu, 13 Nov 2008 09:42:05 GMT


Alexander Martens updated AMQCPP-199:

    Attachment: stress-segfault-1.log.bz2

Got this one with apr-1.3 (apr-util-1.3.4), no stomp and AMQ 5.3-SNAPSHOT:

Core was generated by `python'.
Program terminated with signal 11, Segmentation fault.
#0  0x010a8f9a in activemq::connector::openwire::OpenWireConnector::closeResource (this=0x91f3110,
    at activemq/connector/openwire/OpenWireConnector.cpp:1271
1271                dataStructure = producer->getProducerInfo()->getProducerId();

For some reason producer->producerInfo is NULL (prints at the end of the file).
A reference count problem makes no sense to me at this stage (it should have shown up before),
... odd.

Got the core file, so I can reload if you need more prints.

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