activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Martens (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (AMQCPP-203) Segmentation Fault in Integration tests occurs occasionally.
Date Tue, 04 Nov 2008 08:01:05 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47042#action_47042
] 

alex.martens edited comment on AMQCPP-203 at 11/4/08 12:00 AM:
--------------------------------------------------------------------

Morning Timothy,

By resetting ActiveMQ, it finally completed all 500 loops (/)

I've got three segmentation faults, though. Note that this kind of crash frequency seems to
have been slightly reduced by starting and stopping the server at each loop (from two in 70
to three in 500) - don't ask me why, it might be meaningless.  They are all related to decaf::io::BufferedInputStream::bufferData,
but the first two occurred at the first test just after restarting (was the server fast enough
?), whereas the third one (my favourite) took place on a multiple testMultipleConnections.
I find also helpful the low number of threads involved (at least, compared to what we've working
with).

Iteration #87: core.15348
decaf::io::BufferedInputStream::bufferData (this=0x9404830) at decaf/io/BufferedInputStream.cpp:260
260	        int bytesRead = inputStream->read( getTail(), 0, bytesToRead );

Iteration #152: core.6537
decaf::io::BufferedInputStream::bufferData (this=0x8922830) at decaf/io/BufferedInputStream.cpp:260
260	        int bytesRead = inputStream->read( getTail(), 0, bytesToRead );

Iteration #430: core.10970
decaf::io::BufferedInputStream::bufferData (this=0xb2c2ee20) at decaf/io/BufferedInputStream.cpp:254
254	        std::size_t available = inputStream->available();

Note that I've got all dumped cores, original binaries and many debug symbols, so I can reload
any of those crashes at gdb or even handle them to you. Just tell me if you want them.


      was (Author: alex.martens):
    Morning Timothy,

By resetting ActiveMQ, it finally completed all 500 loops (/)

I've got three segmentation faults, though. Note that this kind of crash frequency seems to
have been slightly reduced by starting and stopping the server at each loop (from two in 70
to three in 500) - don't ask me why, it might be meaningless.  They are all related to decaf::io::BufferedInputStream::bufferData,
but the first two occurred at the first test just after restarting (was the server fast enough
?), whereas the third one (my favourite) took place on a multiple testMultipleConnections.
I find also helpful the low number of threads involved (at least, compared to what we've working
with).

Iteration #87: core.15348
decaf::io::BufferedInputStream::bufferData (this=0x9404830) at decaf/io/BufferedInputStream.cpp:260
260	        int bytesRead = inputStream->read( getTail(), 0, bytesToRead );

Iteration #152: core.6537
decaf::io::BufferedInputStream::bufferData (this=0xb2c2ee20) at decaf/io/BufferedInputStream.cpp:254
254	        std::size_t available = inputStream->available();

Iteration #430: core.10970
decaf::io::BufferedInputStream::bufferData (this=0x8922830) at decaf/io/BufferedInputStream.cpp:260
260	        int bytesRead = inputStream->read( getTail(), 0, bytesToRead );

Note that I've got all dumped cores, original binaries and many debug symbols, so I can reload
any of those crashes at gdb or even handle them to you. Just tell me if you want them.

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


Mime
View raw message