Page History

...

• what are the version numbers of involved software components? (this is very important to detail)
• what platform and JDK?
• any particular container being used? and if so, what version?
• stack traces generally really help! (Remember to post which version of Camel you use, this is important to know when posting stacktraces) 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. 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
• did it work before? what have you changed to break it?
• try upgrading to the latest release and see if it's fixed there
• try the latest SNAPSHOT to see if it's fixed in the pre-release
• search the user forum to see if has been discussed before
• see the "known issues" section in the release notes
• and check the issue tracker to see if the issue has already been reported
• do not send private emails to Camel Team members to ask them to help you faster, or in the private only. Help on Apache Camel is volunteer based and must happen in the open on the public Mailing Lists or Discussion Forums. If  If you want to get help faster or in private, then see further below.

...