zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ZOOKEEPER-597) ASyncHammerTest is failing intermittently on hudson trunk
Date Fri, 04 Dec 2009 23:39:21 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mahadev konar updated ZOOKEEPER-597:
------------------------------------

    Attachment: ZOOKEEPER-597_4.patch

this patch fixes the 2 latest failuires we saw:

- http://bugs.sun.com/view_bug.do?bug_id=6427854, a bug in the jvm which is fixed by a selector.open.close()
call in a static block in NIOServerCnxn (thanks ben for the idea)

- the other cancelled key exception is fixed by wrapping sendbuffer with try catch for exceptions.

i looked for any other calls that can cause commitprocessor to fail in this way and could
not find anything else. hopefully this is the last of such problems.


> ASyncHammerTest is failing intermittently on hudson trunk
> ---------------------------------------------------------
>
>                 Key: ZOOKEEPER-597
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-597
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: tests
>            Reporter: Patrick Hunt
>            Assignee: Benjamin Reed
>            Priority: Critical
>             Fix For: 3.3.0
>
>         Attachments: ZOOKEEPER-597.patch, ZOOKEEPER-597.patch, ZOOKEEPER-597.patch, ZOOKEEPER-597_2.patch,
ZOOKEEPER-597_3.patch, ZOOKEEPER-597_3.patch, ZOOKEEPER-597_4.patch
>
>
> ASyncHammerTest is failing intermittently on hudson trunk. There is no clear reason why
this is happening, but
> it seems from the logs that a session connection to a follower is failing during session
establishment - the
> failure seems to be a problem either on the follower or leader. The server gets the session
create request, but
> it stalls in the request processor pipeline. (we see it go in, but we do not see it com
eout)
> unfortunately all efforts to reproduce this on non-hudson trunk have failed. Even trying
to reproduce by
> running on hudson host itself (manually) has failed.
> We need to instrument the client session creation code in the test to dump the thread
stack if the
> session creation fails.

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