Page History

...

Before asking for help with your issue, it's a very good idea to search for your issue in the mailing list archives and the FAQ. The majority of issues can be solved in this manner without having to send an email to the mailing list. If you don't find an answer, use the guidelines below when writing the e-mailemail.

How to get help

Whenever you are reporting a problem, please be sure to include as much information as possible; the more we know, the better the chance of a quicker resolution.

• which version of the software
• what platform and JDK
• any particular container being used - if so what version
• stack traces generally really help! If in doubt include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. Its It's very easy for us to skim-read past unnecessary parts of a stack trace.
• log output can be useful too; sometimes enabling DEBUG logging can help
• your code & configuration files are often useful

...

• provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?
• submit a patch fixing the bug! (We also buy you beer when we meet you if you submit bug fixes )
• for memory leaks or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if its it's huge) to the JIRA we can normally fix things much faster. e.g. run JProfiler or YourKit on your code and send us the output. To find memory leaks its , it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out whats what's wrong from that.

...