I'm not sure if it matters, but have you tried rewriting the code
with the following:
%@ page import = java.io.*, java.sql.* %
in place of the page element defined below? I've never seen anyone
split up imports
into different statements. Also, as a side note, you don't need
From fusterjj's code!!:
%@ page
import = java.io.*
import = java.lang.*
import = java.sql.*
%
These are three distinct import directives, not one import delimited by
three newlines.
Such a statement would look like:
%@ page
import = java.io.*,
java.sql.*
%
I checked
Whoa, there. Read your code: you're catching a
ClassNotFoundException and printing
out Class loading error. if it occurs. That message comes from your code,
not Tomcat.
Find the line that throws that exception, and I bet you'll find the class
you don't have in
the ClassLoader.
I haven't had a Code Red attack crash my Tomcat server at home.
However, my configuration may vary from yours. On what class of
architecture and type of operating system does your Tomcat server run?
Bill
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Hi Tim,
Open the web.xml which contains the servlet you wish to autoload.
Find the servlet tag that defines that servlet, and inside that stanza,
add a tag like the following:
load-on-startup100/load-on-startup
This will force the servlet to be init'd when the engine
