Tomcat
Documentation
Download
Archives
Jakarta
Get Involved
Misc
|
Before you report a bug
|
The Tomcat community consists of those who use Tomcat, help answer
questions on discussions lists, contribute documentation and patches,
and those who develop and maintain the code for Tomcat. Almost all those
who assist on a day to day basis resolving bug reports do this for a
wide variety of reasons, and almost all of them do this on their own time.
If you have a verified security bug to report please do not post it
to email lists or submit a bug report. Security bugs should be reported
privately by email to security@apache.org.
Many bugs reported end up not being a bug in the Tomcat code, but are
due to misconfiguration, problems caused by installed applications, the
operating system, etc.
Before reporting a bug please make every effort to resolve the problem
yourself.
The remainder of this document points you toward resources you can use to
resolve the problem you are having.
|
|
Resources to help resolve Tomcat problems
|
Here are some resources you can use to help you resolve the
problem you are having before reporting a bug.
Problem trouble shooting
|
Documentation - Review the documentation for the version
of Tomcat you are using. The problem you are having may already
be addressed in the docs.
Logs - The logs which Tomcat generates can be a valuable
resource when trying to diagnose a problem. Please review them.
You may want to enable debug output in your Tomcat configuration
so that you have more information to help diagnose the problem.
FAQ's - Search Frequently Asked Question documents. FAQ's
for all Jakarta projects can be found
here.
|
|
Bug Database
|
Please search the bug database to see if the bug you are
seeing has already been reported.
- The bug may have already been fixed and is available in a later
version or nightly build.
- Someone else may have reported the bug, you could add supporting
information to help reproduce and resolve the bug.
Search the Tomcat 3 bug database
here.
Search the Tomcat 4 bug database
here.
Search the Tomcat 5 bug database
here.
|
|
Tomcat on IRC
|
An IRC channel dedicated to Tomcat exists on OpenProjects.
#tomcat at irc.us.openprojects.net .
Click here to
connect to the channel using Mozilla.
|
|
|
|
Reporting a Tomcat bug
|
If after you have exhausted all other resources to resolve a problem
with Tomcat you may want to file a bug report. Please make sure the
problem is a bug in Tomcat and not a bug in your web application.
Please make sure you provide as much information as possible. Its
very hard to fix a bug if the person looking into the problem can't
reproduce it. Here is a listing of information which should be included:
-
Version - Tomcat version, if from a nightly build, version
and date of build.
-
Tomcat component - Tomcat component which has the bug.
-
Platform - Hardward platform Tomcat is running on.
-
OS - Computer operating system and version.
-
JVM - JVM Version
-
Web Server - Web Server and version, Tomcat Connector and version.
-
Configuration - Attach configuration files if they would help track
down the bug.
-
Log file excerpts - Review your logs files, reproduce the bug with
debugging enabled in your Tomcat configuration. Then submit any relevant
sections of the log which help document the bug.
-
Stack Traces - Any stack traces generated by the bug.
-
Example - Example configuration files or web applications which
demonstrate the bug. When submitting an example which reproduces the bug,
please try to make it as simple as possible.
-
Bug Fix Patch - A patch created using
diff -u which
fixes the bug.
(If you have found a bug fix which can be applied to the Tomcat code)
-
Miscellaneous - Any other information you feel will help track
down the problem. For example other Java API's and versions being used
with Tomcat.
Report a Tomcat 5 bug
here.
Report a Tomcat 4 bug
here.
Report a Tomcat 3 bug
here.
|
|
|