I've just had a rethink on the patches - I think you need to scan the
logs for WARNING level messages from TaskManager containing
"Task.runAfter exception". I just remembered that the current
implementation turns a throw from TaskManager.Task.runAfter into a
warning in the log.
Would it be better to log directly, rather than throw? I can produce a
new patch to do that, maybe at the ERROR level to make sure it will be
noticed?
Patricia
On 7/27/2010 2:10 PM, Peter Firmstone wrote:
QA Test Results:
[java] -----------------------------------------
[java]
[java] # of tests started = 397
[java] # of tests completed = 397
[java] # of tests skipped = 18
[java] # of tests passed = 397
[java] # of tests failed = 0
[java]
[java] -----------------------------------------
[java]
[java] Date finished:
[java] Wed Jul 28 00:12:51 EST 2010
[java] Time elapsed:
[java] 11686 seconds
Timezone GMT +10 (Australia)
Jtreg tests to follow.
Cheers,
Peter.
Patricia Shanahan wrote:
Please let me know if and when you have looked at the patch, and if
there are any problems with it, because I'm working on more, similar,
tests.
Also, what is your time zone? It affects the meaning of "tomorrow".
I'm in California.
Patricia
Peter Firmstone wrote:
I'll have the results of the tests tomorrow.
Cheers,
Peter.
Patricia Shanahan (JIRA) wrote:
[
https://issues.apache.org/jira/browse/RIVER-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patricia Shanahan updated RIVER-344:
------------------------------------
Attachment: first_test.patch
This is the first in a series of test patches for probing behavior
of TaskManager users. Feel free to change the RuntimeException throw
to anything you prefer that will be easily recognized during testing.
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: first_test.patch
The current implementation of TaskManger doesn't scale.
