Alexey N. Solofnenko wrote:
Maybe just ioex.printStackTrace()?
I thought it would be better to log to the specific calling task (although getting the error message from the exception makes perfect sense). I seem to recall a complaint about close silent behaviour with a full filesystem and it taking a *long* time to track down the cause of the strange failure, that's the motivation behind the suggestion.
Kev --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
