RE: Initial JDBC Hits to AS/400 DB using Tomcat is Very Slow?

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Chad,

I am not sure why you are seeing so many compiles. Building JSP pages
should be a one time charge. The jasper compiler looks at the date of
the generated class and compares that to the date of the .jsp source
page and compiles when the generated class is stale. Restarting the
system should not cause the page to recompile. Do you clear the work
directory or push out .jsp pages on a restart?

David Morris 


-----Original Message-----
From: cornelius, chad [mailto:chad.cornelius@xxxxxxxxxxxxxxxxxxxx] 
Sent: 16 December 2003 14:20
To: 'JAVA400-L@xxxxxxxxxxxx' 
Subject: Initial JDBC Hits to AS/400 DB using Tomcat is Very Slow?


Does anyone know what would cause initial JDBC hits on an AS/400 DB to
perform slowly using Tomcat?  I have setup Tomcat to use connection
pooling
just as David suggests in his article, "Tomcat on iSeries", which is
very
good by the way.  I have compiled all the .jar files, but Tomcat still
performs slowly on the first hits.  Our AS/400's shutdown nightly to
perform
backups, so I am not sure if this is the cause.  After one hit is made
to a
table, all other hits are very fast.  It's just the first hit in the
morning.  My other thought is that we do not have the SQL package on
our
AS/400, which allows you to perform the STRSQL command.  Would this be
another reason?  It seems JDBC would be independent of that.  Does
anyone
have any suggestions?  Any help would be greatly appreciated.

 

Thanks,

Chad