You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Andera Del Bene (JIRA)" <ji...@apache.org> on 2011/07/13 14:36:59 UTC

[jira] [Updated] (WICKET-3893) Possible deadlock running AsynchronousDataStoreTest

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

Andera Del Bene updated WICKET-3893:
------------------------------------

    Attachment: AsynchronousTest.patch

> Possible deadlock running  AsynchronousDataStoreTest
> ----------------------------------------------------
>
>                 Key: WICKET-3893
>                 URL: https://issues.apache.org/jira/browse/WICKET-3893
>             Project: Wicket
>          Issue Type: Test
>          Components: wicket-core
>            Reporter: Andera Del Bene
>         Attachments: AsynchronousTest.patch
>
>
> Running AsynchronousDataStoreTest on "slow" pc (i.e. dual core 2 GhZ, 2 Gb of ram) AsynchronousDataStoreTest doesn't terminate at all. I think that problem occurs when we submit a task which has been already submitted but not executed yet. This leads to a missed latch countdown.
> The problem doesn't occur when I decrease EXECUTIONS variable.
> A possible fix is to replace latch with a calling to awaitTermination method.
> I attach a patch.   

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira