[
https://issues.apache.org/activemq/browse/AMQCPP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47051#action_47051
]
Timothy Bish commented on AMQCPP-203:
-------------------------------------
I think I see what is going on here. The problem is confined to the shut-down
portion of the client. There's some contention when closing the socket and
shutting down the threads where some pointers get deleted and the socket calls
get signalled by closing the socket.
The attached patch may help with the BufferedInputStream error. The failure on
available is a bit tricky because I'm not sure yet what part of that call is
causing the seg fault, there's a lot of OS level calls to the socket functions.
The buffered stream was having is data buffer deleted in its close method
which was bad since the read thread in IOTransport could still be in the middle
of calling a read and not yet blocked on the socket.
> Segmentation Fault in Integration tests occurs occasionally.
> ------------------------------------------------------------
>
> Key: AMQCPP-203
> URL: https://issues.apache.org/activemq/browse/AMQCPP-203
> 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: 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.
