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

["Bruce Jin" <brucej@xxxxxxxxxxxxxxxxxxxx>]

To avoid servlet/jsp lazy loading (first hit slowdown) you could specify
<load-on-startup> in web.xml when registering your servlet/jsp to the
container.





> Patrick,
>
> It is a jsp page.  I don't know much about the 400 commands.  What does
> QJVAEXEC tell you?
>
> Thanks,
> Chad
>
>
> -----Original Message-----
> From: Patrick L Archibald [mailto:Patrick.Archibald@xxxxxxxxxxxxx]
> Sent: Tuesday, December 16, 2003 7:45 AM
> To: Java Programming on and around the iSeries / AS400
> Subject: Re: Initial JDBC Hits to AS/400 DB using Tomcat is Very Slow?
>
> Is it a servlet or a jsp page? If it is a jsp page the delay may be the
> compilation of the jsp page into the servlet.  Look for a jobs called
> QJVAEXEC with WRKSYSACT in automatic refresh mode when you first access
> the page. (You may not have WRKSYSACT. I think it is part of Performance
> tools. If so, use WRKACTJOB instead.)  JSP page compilation is my
> biggest performance hit.
>
> Thanx, PLA
>
> cornelius, chad wrote:
>
> >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.
> >
> >
>