activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQCPP-203) Segmentation Fault in Integration tests occurs occasionally.
Date Wed, 05 Nov 2008 18:33:05 GMT


Timothy Bish commented on AMQCPP-203:

All these segfaults today are really killing the post election buzz. :)

The DeacfRuntime error seems to be in the APR's global pool destroy, not sure what is going
on in there, I know it creates its own mutex to try and protect the pool from corruption.

The BufferInputStream error is tricky, do you know if the error actually occurs on the call
to available, or is it actually inside the available call.  Trying to determine if the underlying
SocketInputStream pointer has become invalid or if its something in the available call that's
choking because the socket handle was closed.

> Segmentation Fault in Integration tests occurs occasionally.
> ------------------------------------------------------------
>                 Key: AMQCPP-203
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Sub-task
>          Components: Integration Tests
>    Affects Versions: 2.2.1
>         Environment: CentOS 5.2 / REHL / Fedora 9
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 2.2.2
>         Attachments: BufferedInputStream.cpp.patch, segfault.6517.tar.gz, segfault.bufferedinputstream.log.gz,
segfaults.barak.tar.gz, segfaults.tar.gz
> While running the integration tests in a long loop an occasional Segmentation fault has
been seen. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message