[
https://issues.apache.org/activemq/browse/AMQCPP-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-199:
-------------------------------------
Attachment: stress-again.tar.gz
Hi.
Something went wrong - I'm not sure what it is, though. It all started with a
failing stomp test and after that, almost everything else failed, even closing
the server. My previous version test with apr (trunk) and amq (trunk) worked
fine, though.
I'm about to comment all stomp tests, stick to apr 1.3 and rerun with the
server's trunk version.
As long as we stick to Openwire, it should work,...
> 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
> Fix For: 2.2.2
>
> Attachments: python.stress.log.gz, stress-again.tar.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/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.
