FAQ / Bugs
If you think you found a bug, read this page.
I have a bug, what do I do?
Unless you have the source code reference in Tomcat which is wrong, it may not be a bug. E-mail the Tomcat user list and confirm its a bug. Also read this first from the tomcat site about reporting a bug.
Why does feature ABC work in Servlet Container XYZ but not in Tomcat?
There could be a good chance that the other servlet container could be implementing the spec wrong.
I submitted a bug, why is it ignored?
- Any of the following may affect someone acting on a bug:
- Is it a bug?
- Is your description good?
- Is your description complete?
Can a developer easily reproduce the bug in their own environment?
Have you provided a patch? Is it against the current sources from svn? Using the correct file? Using svn diff or diff -u ?
- Is your patch coded well?
- Is your solution "good"?
Some developers are uncomfortable submitting patches to code they are unfamiliar with. The committers are not experts in all areas of Tomcat. It may be that the developer who has the ability to adequately review the patch may be too busy or unable to review the bug. That is the bad news, the good news is Tomcat is Open Source and you can build and use your own release until the fix gets back into the official release.
What does it mean to contact the user list?
If you are reading this - you were probably instructed to contact the user list for help. Bugzilla is not a support forum. Bugzilla is intended to fix "real bugs" in Tomcat. It is not intended to help you diagnose errors you are experiencing. The outcome of a diagnosis can be a new bug in Bugzilla. Configuration questions do not belong in Bugzilla. See Tomcat User for what the Tomcat User list is.