[jira] [Commented] (RIVER-344) com.sun.jini.thread.TaskManager scalability and concurrency.

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on RIVER-344:
------------------------------

FAILURE: Integrated in River-trunk-jdk7 #153 (See [https://builds.apache.org/job/River-trunk-jdk7/153/])
RIVER-344

Implemented Comparable for all tasks relying on order, removed Comparator's to avoid unnecessarily adding to public API.

Set up sensible defaults for ThreadPoolExecutor implementations of ExecutorService, this will cause some test failures for tests that make assumptions about serial event generation and delivery above and beyond the Jini Event specification, for Reggie, note these failures do not occur when ThreadPoolExecutors are configured to be single threaded.

Documentation of configuration options to follow. (peter_firmstone: [http://svn.apache.org/viewvc/?view=rev&rev=1557708])
Cleaned up synchronization and locking strategies and removed instances of synchronization while performing remote calls.

Changed final fields to non final where "this" escaped during construction.

Replaced TaskManager with ExecutorService where Task.runAfter was not required, TaskManager is still utilised by JoinManager, ServiceDiscoveryManager and the qa test framework.
Changed TaskManager to accept Runnable and to check for Task instances.

Changed RetryTask, pushed TaskManager.Task implementations to subclasses that used it.  RetryTask is not compatible with Task.runAfter as documented in River-344.

Added Generics to static configuration methods, to eliminate casts.

Started working on ScheduledExecutors to take advantage of a ScheduledExecutorService to allow sharing of a thread pool for tasks that have dependencies, require order and must not execute until their dependencies have completed. (peter_firmstone: [http://svn.apache.org/viewvc/?view=rev&rev=1554723])


> com.sun.jini.thread.TaskManager scalability and concurrency.
> ------------------------------------------------------------
>
>                 Key: RIVER-344
>                 URL: https://issues.apache.org/jira/browse/RIVER-344
>             Project: River
>          Issue Type: Sub-task
>          Components: com_sun_jini_thread
>         Environment: All
>            Reporter: Peter Firmstone
>         Attachments: TaskManager_uses.docx, TaskManager_uses.pdf, first_test.patch, full_test.patch, jtreg_tests.tgz, jtreg_tests2.tgz, qa_test_results.gz, qa_test_results2.gz
>
>
> The current implementation of TaskManger doesn't scale.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)