Are you sure that under Tomcat the application is really using the Tomcat connection pool? If not that would certainly account for the differences. Even if Tomcat DBCP is configured, checking that the pool configurations are similar would seem like an important check.
-Brett On Mon, Apr 13, 2015 at 4:56 PM, Øyvind Harboe <oyvind.har...@zylin.com> wrote: > I know the Tomcat setup isn't using the clientdriver when it slows > down, because when I first tried to switch to the ClientDriver it > failed. After I copied the derbyclient.xxx.jar to tomcat/lib/, it > worked. > > > > > > On Mon, Apr 13, 2015 at 9:51 AM, Dyre Tjeldvoll > <dyre.tjeldv...@oracle.com> wrote: > > On 04/13/2015 12:27 AM, Øyvind Harboe wrote: > >> > >> I found another crucial clue: > >> > >> if I use ClientDriver instead of EmbeddedDriver and connect to the > >> Derby database running under Jetty, I get identical performance with > >> Tomcat and Jetty. > >> > >> This is very strong indication that there is something about the > >> combination of EmbeddedDriver and Tomcat that is gumming up the works. > > > > > > Could it be that your Tomcat setup always uses the ClientDriver for some > > reason? I don't know much about setting up Databases with AppServers, but > > based on the number of questions on SO and other places, it isn't > trivial... > > > > -- > > Regards, > > > > Dyre > > > > -- > Øyvind Harboe - Can Zylin Consulting help on your project? > http://www.zylin.com/ >
