possible resource leak while using Derby DRDA + IBM DB2 Universal Driver???

(embedding Derby in a C-CJDBC controller) in the same configurations and it demonstrated a constant/average access time of approx 8.33ms per 1000x So I believe there to be a problem in either the client-side, or server-side DRDA code ... Has anyone else seen this behavior? Regards - Larry Cable

RESEND: possible resource leak in either Derby DRDA or IBM DB2 Universal JDBC Driver

(min: 7.86, max 10.16) Although I cannot (yet) identify where the problem is, I believe there must be some problem in either the DB2 client or the derby server DRDA implementation ... anyone got any ideas/comments? - Larry Cable __ Do you