derby.log and multiple class loaders

[Katherine Marsden]

Hell Derby Users,

I am curious how people address the issue of derby.log in multiple class 
loader environments to avoid the two class loaders clobbering each 
other's error logs.

I was thinking perhaps best practice would be to use 
derby.stream.error.method or derby.stream.error.field to construct 
something unique like derby.log.<classloader hash code> but am curious 
if others have and how they have addressed the shared error log in 
multiple class loader environments.


Thanks

Kathey