river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RIVER-391) Outrigger failure under stress
Date Mon, 06 Jun 2011 16:18:59 GMT

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

Tom Hobbs resolved RIVER-391.
-----------------------------

    Resolution: Fixed
      Assignee: Patricia Shanahan

Fix is complete.  Fixer is unhappy with level of stress testing, but increasing those levels
should be in another task.

> Outrigger failure under stress
> ------------------------------
>
>                 Key: RIVER-391
>                 URL: https://issues.apache.org/jira/browse/RIVER-391
>             Project: River
>          Issue Type: Bug
>          Components: com_sun_jini_outrigger
>    Affects Versions: River_2.1.2
>            Reporter: Patricia Shanahan
>            Assignee: Patricia Shanahan
>             Fix For: River_2.2.0
>
>         Attachments: FastListTest.java
>
>
> Hudson produced a single QA failure running com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.td.
The frequency can be increased by increasing the degree of stress, by adding more readers,
writers, and entries:
>  com.sun.jini.test.share.restart_wait=10000
> -com.sun.jini.test.impl.outrigger.matching.StressTest.num_entries=1000
> -com.sun.jini.test.impl.outrigger.matching.StressTest.num_readers=13
> -com.sun.jini.test.impl.outrigger.matching.StressTest.num_writers=7
> +com.sun.jini.test.impl.outrigger.matching.StressTest.num_entries=10000
> +com.sun.jini.test.impl.outrigger.matching.StressTest.num_readers=500
> +com.sun.jini.test.impl.outrigger.matching.StressTest.num_writers=500
>  com.sun.jini.test.impl.outrigger.matching.tryShutdown=1

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

Mime
View raw message