> failed to do that ("no appenders could be found for
> org.firebirdsql.jca.IdleRemover", props file copied from wiki faq and
> from posts here, maybe -DFBLog4j=true was not set properly).

Hmmm.... check also the jar file itself, if it contains log4j.properties,
just remove them from there.

> i have no source of my version of jaybird.

You can get them from the CVS - tag is JayBird_1_0_1 (or JayBird_1_0_0, but
most likely former). Unfortunately there were no source distribution for
1.0.

> lack of time. I noticed that the interface has slightly changed,
> didnt want to rewrite anything. but now I see that I waste more time
> to make old stuff work with 1.5.2 :-/

If I remember correctly, JayBird 1.5.x is backward compatible on interface
level with JayBird 1.0.1, JayBird 2.0.x is not.

> yes, the server was 1.5.1 ss, now is 1.5.2.4731 cs... :-/ am I an
> idiot? :)))

I asked that because of some "fatal" error that happens. JayBird 1.0.x and
1.5.x have one not very nice property - if an error happens that is in so
called "fatal error list", the underlying connection is closed. If that
happens somewhere between transactions, driver instead of marking the
connection object as closed simply re-establish the underlying physical
connection. This was a source of unexplainable errors for a long time and
this "feature" is removed in 2.0. The list of "fatal errors" is quite long,
and I vaguely remember there were some error reports because of server
version change (though that was, if I'm correct, transition from FB 1.0 to
FB 1.5, or from IB 6.0 to FB 1.5, something like that).

Roman