The specification for Fiddler is defined not only by the River Lookup
Discovery Service Specification, but also by the API
documentation (generated by the Javadoc(TM) tool) for
org.apache.river.fiddler.FiddlerAdmin
and
net.jini.admin.Administrable.
A full list of supported configuration entries is given in this service's man page.
Logger
for each type of information logged. The name of each logger
is a dot-separated concatenation of the implementation package name,
org.apache.river.fiddler, with a descriptive string. A description of each
logger used by this service, as well as what information is logged to which
logger, and at what logging level, is given in this service's
man page.
register method, if null
is passed as the value of the locators parameter,
a NullPointerException occurs.
This bug has been fixed.
getLocator on the discovered lookup service. That
comparison is done using LookupLocator.equals.
LookupLocator.equals employs a case-insensitive string
compare of the host names of the locators to determine equality. Thus,
if one locator is associated with a hostname of "myHost",
and the other locator is associated with a fully qualified hostname like
"myHost.myCompany.com", LookupLocator.equals will return
false, and Fiddler will view as different, locators that
should actually be considered the same.
To address this bug, the implementation in this release now employs
the same strategy that URL currently employs. That is,
it first applies LookupLocator.equals (to do a case-insensitive
string compare). If the call to LookupLocator.equals returns false, then the IP addresses associated with each locator
are retrieved and compared to determine equality.
Thread.interrupt method to set an "interrupted" field are
susceptible to lost interrupts. This is because java.util.logging
swallows internal InterruptedIOExceptions without setting
the receiving thread's interrupted status; effectively 'forgetting' the
interrupt that occurred. The end result is that some of Fiddler's threads could endlessly loop instead of terminate, causing shutdown processing
in Fiddler to hang.
This bug has been fixed.
setLocators method), the result was the opposite
of what the specification prescribes. That is, the
locators-of-interest were not replaced at all.
This bug has been fixed.
To address this issue, Fiddler now handles such "early" calls by blocking until initialization completes.
null; throwing an exception if
a null value were entered. (Note that if the entry
were simply absent from the configuration, Fiddler interpretted
this as an indication that no JAAS login should be performed.)
To address this issue, Fiddler now interprets a null
value for the loginContext entry, as well as an absent
entry, as an indication that a JAAS login should not be performed.
Fiddler Has 3 Modes of Execution
org.apache.river.fiddler
package documentation.