On Thu, 14 Feb 2008, Mark Taylor wrote:
> On Thu, 14 Feb 2008, Matthijs H.D. van der Wiel wrote:
>
>> ~/data/SLS/M07BN03 >Feb 14, 2008 9:31:11 AM
>> uk.ac.starlink.splat.imagedata.NDFJ <clinit>
>> WARNING: Failed to load the Starlink SPLAT-VO JNI library
>> "
>
> Peter,
>
> a quick scan of the NDFJ source suggests that you might get some better
> diagnostic help from the error reporting if the logging level was upped
> to CONFIG. I can't remember off hand the incantation to do this at
> runtime, and I'm a bit snowed under just now, but I'm sure you can find
> it in the java.util.logging docs.
>
> Supplementary - I've got a feeling that the Loader.loadLibrary() method
> which is probably where the problem originates isn't as good as
> it could be about logging exceptions either (my fault). Feel free
> to tinker if it looks like a good idea.
Hi Mark,
think what Loader gets up to is fine, as you say the real problem here is
the default logging system setup.
Matthijs, could you change the "logging.properties" file in
"star/starjava/etc" so that the part that says:
# Set the default level for logging from Starlink loggers.
uk.ac.starlink.level = INFO
is changed to:
# Set the default level for logging from Starlink loggers.
uk.ac.starlink.level = CONFIG
java.util.logging.ConsoleHandler.level = CONFIG
That will write the full exception about why any JNI libraries to the
console (so you will need to start SPLAT in a terminal window).
Cheers,
Peter.
--
Peter W. Draper, http://astro.dur.ac.uk/~pdraper
|