That looks interesting, but this appears to only be for error messages.  Do *all* derby.log messages get written to this stream, and when they are, are they not written to derby.log?

If you don't know off-hand, that's fine, it's easy enough for me to test...

Thanks!

David

On Mon, May 10, 2010 at 4:22 PM, Dag H. Wanvik <Dag.Wanvik@sun.com> wrote:
David Van Couvering <david@vancouvering.com> writes:

> I have a service that shuts down the Derby database after it is done using
> it.  This is because on Linux I was getting errors "too many open files"
> unless I did this - I use a lot of databases, and when all of them are
> booted it starts using up too many resources.
>
> But now my problem is that every time I shut down a DB, and every time I
> boot a DB, it adds a message to the derby.log file, and over time the log
> file grows and grows.  Is there any way to silence these messages?

I don't know any switch for it, but I perhaps you could leverage
derby.stream.error.method to filter away the output you don't want, by
building your own stream impl.

http://db.apache.org/derby/docs/10.5/ref/rrefproper35028.html

Dag

>
> Here is an example:
>
> ----------------------------------------------------------------
> 2010-05-10 20:35:55.703 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby -
> 10.5.3.0 - (802917): instance a816c00e-0128-83ee-5a69-00002248f366
> on database directory
> C:\Vontu\Protect\scan\incremental_index\MONITOR_TARGET_11
>
> Database Class Loader started - derby.database.classpath=''
>
> 2010-05-10 20:35:56.172 GMT:
> Shutting down instance a816c00e-0128-83ee-5a69-00002248f366
> ----------------------------------------------------------------
> ----------------------------------------------------------------
> 2010-05-10 20:35:56.188 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby -
> 10.5.3.0 - (802917): instance 6839c016-0128-83ee-5a69-00002248f366
> on database directory
> C:\Vontu\Protect\scan\incremental_index\MONITOR_TARGET_12
>
> Database Class Loader started - derby.database.classpath=''
>
> 2010-05-10 20:35:56.235 GMT:
> Shutting down instance 6839c016-0128-83ee-5a69-00002248f366
> ----------------------------------------------------------------
> ----------------------------------------------------------------
> 2010-05-10 20:35:56.235 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby -
> 10.5.3.0 - (802917): instance 286cc01e-0128-83ee-5a69-00002248f366
> on database directory
> C:\Vontu\Protect\scan\incremental_index\MONITOR_TARGET_11
>
> Database Class Loader started - derby.database.classpath=''
>
> 2010-05-10 20:35:56.282 GMT:
> Shutting down instance 286cc01e-0128-83ee-5a69-00002248f366
> ----------------------------------------------------------------
> ----------------------------------------------------------------
> 2010-05-10 20:35:56.297 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby -
> 10.5.3.0 - (802917): instance e8afc026-0128-83ee-5a69-00002248f366
> on database directory
> C:\Vontu\Protect\scan\incremental_index\MONITOR_TARGET_12
>
> Database Class Loader started - derby.database.classpath=''
>
> 2010-05-10 20:35:56.344 GMT:
> Shutting down instance e8afc026-0128-83ee-5a69-00002248f366
> ----------------------------------------------------------------
>
> --
> David W. Van Couvering
>
> http://www.linkedin.com/in/davidvc
> http://davidvancouvering.blogspot.com
> http://twitter.com/dcouvering

--
Dag H. Wanvik, staff engineer
Sun Microsystems, Java Core and Desktop - Java DB/Derby
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101
Sun IM: dw136674, Yahoo IM: dag_h_wanvik



--
David W. Van Couvering

http://www.linkedin.com/in/davidvc
http://davidvancouvering.blogspot.com
http://twitter.com/dcouvering