On 9/12/2010 3:43 AM, Peter Firmstone wrote:
Patricia Shanahan wrote:
On 9/11/2010 10:49 PM, Peter Firmstone wrote:
...
My current tests are running with FINEST enabled, they might show up
some RetryTask log messages, I'll check & let you know when they're
complete.
Excellent. Even an absence of retry messages would be useful
information, meaning that we are not testing retries.
Good news, although repeat testing (with RetryTask logging set to
FINEST) is still underway, I'm getting a number of hits:
bash-3.00$ grep "retry of" out2.txt
[java] FINEST: retry of
net.jini.discovery.lookuplocatordiscovery$discoveryt...@1fddc31 in
20,000 ms
[java] FINEST: retry of
net.jini.discovery.lookuplocatordiscovery$discoveryt...@1fddc31 in
30,000 ms
[java] FINEST: retry of
net.jini.discovery.lookuplocatordiscovery$discoveryt...@ce2187 in 20,000 ms
...
This is indeed good news. I still need to find out what went wrong with
my attempt to enable the logging, but that is a minor issue.
When your run finishes, could you make the log available to me? If it
seems too big to e-mail, put it on-line somewhere. I want to read some
of the tests that are getting retries to see how they are doing it.
Thanks,
Patricia
