[
https://issues.apache.org/activemq/browse/AMQCPP-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47434#action_47434
]
Alexander Martens commented on AMQCPP-199:
------------------------------------------
After successfully running the first loop with its 100 passes, stopping and
restarting the server, it got locked during the second loop, at the 29th pass,
inside test_sessions_with_message_listeners
(test_openwire_async.test_openwire_async).
I'm about to retry with 50 passes per loop tonight, as gdb shows nothing
interesting (just seems to be waiting for a message to come).
No segmentations faults though.
> 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-segfault-1.log.bz2, 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.
