× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David,

Thanks for the reply.  I don't believe I am doing anything special.  I
assume clearing the working directory and the push out would take place in
the web.xml file.  The only thing that I am doing in there is as follows:
<!DOCTYPE web-app 
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" 
    "http://java.sun.com/dtd/web-app_2_3.dtd";>

<web-app>

    <display-name>Eclipse Application</display-name>
    <description>Application that implements Judicial's Case
Class</description>
    
    <servlet>
        <servlet-name>custjsp</servlet-name>
        <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
        <init-param>
            <param-name>logVerbosityLevel</param-name>
            <param-value>WARNING</param-value>
        </init-param>
        <init-param>
            <param-name>fork</param-name>
            <param-value>false</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>
                
    <servlet>
        <servlet-name>DBHandler</servlet-name>
        <servlet-class>com.state.judicial.db.DBHandler</servlet-class>
    </servlet>
    
    <servlet>
        <servlet-name>SumServlet</servlet-name>
        <servlet-class>com.state.judicial.servlet.SumServlet</servlet-class>
    </servlet>

                <!-- The mapping for the JSP servlet -->
    <servlet-mapping>
        <servlet-name>custjsp</servlet-name>
        <url-pattern>*.jsp</url-pattern>
    </servlet-mapping>
                
    <servlet-mapping>
        <servlet-name>DBHandler</servlet-name>
        <url-pattern>/com/state/judicial/db/DBHandler</url-pattern>
    </servlet-mapping>

    <servlet-mapping>
        <servlet-name>SumServlet</servlet-name>
        <url-pattern>/com/state/judicial/servlet/SumServlet</url-pattern>
    </servlet-mapping>
    
    <resource-ref>
                <description>
                Resource reference to java.sql.Connection factory defined in
server.xml
                </description>
                <res-ref-name>jdbc/as400</res-ref-name>
                <res-type>javax.sql.DataSource</res-type>
                <res-auth>Container</res-auth>
                </resource-ref>
                
                <!-- <resource-ref>
                <description>
                Resource reference to java.sql.Connection factory defined in
server.xml
                </description>
                <res-ref-name>jdbc/db2</res-ref-name>
                <res-type>javax.sql.DataSource</res-type>
                <res-auth>Container</res-auth>
                </resource-ref> -->

</web-app>

The load-on-startup bit was something I thought I would try to improve the
situation.

Thanks,
Chad


-----Original Message-----
From: David Morris [mailto:David.Morris@xxxxxxxxxxxxx] 
Sent: Wednesday, December 17, 2003 1:16 PM
To: java400-l@xxxxxxxxxxxx
Subject: RE: Initial JDBC Hits to AS/400 DB using Tomcat is Very Slow?

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

_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.