jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-78) waitForCommit() test failure for MK remoting
Date Mon, 30 Apr 2012 08:31:45 GMT

    [ https://issues.apache.org/jira/browse/OAK-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264728#comment-13264728
] 

Dominique Pfister commented on OAK-78:
--------------------------------------

> There doesn't seem to be any need for synchronization in Client (the server
> should in any case be thread-safe), so I think we should just unsynchronize
> the Client method.

Wrong, the javadoc for the Client class clearly says:

  "All public methods inside this class are completely synchronized because"
  "HttpExecutor is not thread-safe."

                
> waitForCommit() test failure for MK remoting
> --------------------------------------------
>
>                 Key: OAK-78
>                 URL: https://issues.apache.org/jira/browse/OAK-78
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mk
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.2
>
>
> The .mk.client.Client class is synchronized, which makes it fail the new waitForCommit()
integration test.
> There doesn't seem to be any need for synchronization in Client (the server should in
any case be thread-safe), so I think we should just unsynchronize the Client method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message