Author: buildbot
Date: Tue Jul 11 08:20:00 2017
New Revision: 1015242
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/how-can-i-get-help.html
websites/production/camel/content/irc-room.html
websites/production/camel/content/support.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/how-can-i-get-help.html
==============================================================================
--- websites/production/camel/content/how-can-i-get-help.html (original)
+++ websites/production/camel/content/how-can-i-get-help.html Tue Jul 11
08:20:00 2017
@@ -75,7 +75,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2
id="HowcanIgethelp-GettingHelp">Getting Help</h2><p>If you are experiencing
problems using Camel then please report your problem to our mailing list. This
allows the entire community to help with your problem. If indeed a bug has been
identified in the Camel software, then document the problem in our <a
shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a>. Please
refrain from immediately opening a ticket in the issue tracker unless you are
certain it's a problem in the Camel software. If you are in doubt, we
appreciate asking the mailing list first.</p><div
class="confluence-information-macro confluence-information-macro-tip"><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Please read the section below
(<em>How to get help</em>), and follow the bullets advised there
first.</p></div></div
><div class="confluence-information-macro
>confluence-information-macro-information"><p class="title">Reporting bugs -
>Please read this first</p><span class="aui-icon aui-icon-small
>aui-iconfont-info confluence-information-macro-icon"></span><div
>class="confluence-information-macro-body"><p>We prefer people to get in touch
>first using the mailing list. Or take time to read FAQs, or search in the
>mailing list archives to find answers.<br clear="none"> Unfortunately some
>people create a JIRA ticket as first thing. Please don't do that! Only if you
>are sure it really is a bug etc. JIRA tickets create noise<br clear="none">
>for the Camel team to react on issues that are not bugs. But already covered
>in FAQs, in the mailing lists etc. Or in the existing documentation.<br
>clear="none"> Also on the mailing lists there is more people active to help
>you better.</p></div></div><ul><li><a shape="rect" class="external-link"
>href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a></li>
<li><a shape="rect" href="faq.html">FAQ</a></li></ul><h3
id="HowcanIgethelp-Alternativediscussionforums">Alternative discussion
forums</h3><p>There's a number of sites outside Apache that offer discussion
forums on Camel. For example, <a shape="rect" class="external-link"
href="http://stackoverflow.com/"; rel="nofollow">Stack Overflow</a> is a popular
Q & A site with a <a shape="rect" class="external-link"
href="http://stackoverflow.com/questions/tagged/apache-camel";
rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find
helpful discussions on technical blogs, on <a shape="rect"
class="external-link" href="https://www.google.com/search?q=apache+camel";
rel="nofollow">Google</a>, or even on <a shape="rect" class="external-link"
href="https://twitter.com/#!/search/apache%20camel";
rel="nofollow">Twitter</a>.</p><h3
id="HowcanIgethelp-Usingdeprecatedcomponents">Using deprecated
components</h3><p>Deprecated components are <strong>not</strong> suppor
ted and issues such as bugs may not be fixed. We encourage users to migrate
away from using any deprecated component. A list of deprecated components is
listed on the github page at: <a shape="rect" class="external-link"
href="https://github.com/apache/camel/tree/master/components#components";
rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3
id="HowcanIgethelp-Howtogethelp">How to get help</h3><p>Before you report a
problem, you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br
clear="none"> When you report an issue, please be sure to include as much
information as possible. The more we know, the easier it is to reach an
effective solution quickly.</p><div class="confluence-information-macro
confluence-information-macro-note"><p class="title">What version do you
use</p><span class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>What
version of Camel do you use! Remember to include this
information.</p></div></div><ul><li><strong>what are the version numbers of
involved software components?</strong> (this is very important to
detail)</li><li>what platform and JDK?</li><li>any particular container being
used? and if so, what version?</li><li>stack traces generally really help!
(<strong>Remember to post which version of Camel you use, this is important to
know when posting stacktraces</strong>) 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.</li><li>log output can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can
help</li><li>your code & configuration files are often useful</li><li>did
it work before? what have you changed to break it
?</li><li>try upgrading to the latest release and see if it's fixed
there</li><li>try the latest SNAPSHOT to see if it's fixed in the
pre-release</li><li>search the user forum to see if has been discussed
before</li><li>see the "known issues" section in the release notes</li><li>and
check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the issue has already been reported</li><li>do <strong>not</strong> send
private emails to Camel <a shape="rect" href="team.html">Team</a> members to
ask them to help you faster, or in the private only. Help on Apache Camel is
volunteer based and <strong>must</strong> happen in the <strong>open</strong>
on the public <a shape="rect" href="mailing-lists.html">Mailing
Lists</a>. If you want to get help faster or in private, then see further
below.</li></ul><h3 id="HowcanIgethelp-Howtogethelpfaster">How to get help
faster</h3><p>We can help you much quicker if you try the follow
ing</p><ul><li>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?</li><li><a shape="rect" class="external-link"
href="http://camel.apache.org/contributing.html";>submit a patch</a> fixing the
bug! (We also buy you beer when we meet you if you submit bug fixes <img
class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak 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 it's huge) to the JIRA we can
normally fix things much faster. e.g. you could run <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html";
rel="nofollow">jmap</a>/<a shape="rect" class="external-link"
href="http://java.sun.
com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>,
JProfiler or YourKit on your code and send us the output. To find memory leaks
it's quicker to resolve if you can tell us what classes are taking up all of
the RAM; we can normally figure out what's wrong from that.</li></ul><h2
id="HowcanIgethelp-CommercialSupport">Commercial Support</h2><p>This is an open
source project, so the amount of time we have available to help resolve your
issue is often limited as all help is provided on a volunteer basis. If you
want to get priority help, need to get up to speed quickly, require some
training or mentoring, or need full 24 x 7 production support you could contact
one of the following companies with <a shape="rect"
href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div>
+<div class="wiki-content maincontent"><h2
id="HowcanIgethelp-GettingHelp">Getting Help</h2><p>If you are experiencing
problems using Camel then please report your problem to our mailing list. This
allows the entire community to help with your problem. If indeed a bug has been
identified in the Camel software, then document the problem in our <a
shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a>. Please
refrain from immediately opening a ticket in the issue tracker unless you are
certain it's a problem in the Camel software. If you are in doubt, we
appreciate asking the <a shape="rect" class="external-link"
href="http://camel.apache.org/mailing-lists.html";>mailing list</a>, <a
shape="rect" class="external-link"
href="http://camel.apache.org/irc-room.html";>IRC chat</a>, or <a shape="rect"
class="external-link" href="https://gitter.im/apache/apache-camel";
rel="nofollow">Gitter chat</a> first.</p><div class="confluence-information-macr
o confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Please read the section below
(<em>How to get help</em>), and follow the bullets advised there
first.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Reporting bugs -
Please read this first</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>We prefer people to get in touch
first using the <a shape="rect" class="external-link"
href="http://camel.apache.org/mailing-lists.html";>mailing list</a>, <a
shape="rect" class="external-link"
href="http://camel.apache.org/irc-room.html";>IRC chat</a> or <a shape="rect"
class="external-link" href="https://gitter.im/apache/apache-camel";
rel="nofollow">Gitter chat</a>. Or take time to read FAQs, or searc
h in the mailing list archives to find answers.<br clear="none"> Unfortunately
some people create a JIRA ticket as first thing. Please don't do that! Only if
you are sure it really is a bug etc. JIRA tickets create noise<br clear="none">
for the Camel team to react on issues that are not bugs. But already covered in
FAQs, in the mailing lists etc. Or in the existing documentation.<br
clear="none"> Also on the mailing lists there is more people active to help you
better.</p></div></div><ul><li><a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a></li><li><a
shape="rect" href="faq.html">FAQ</a></li></ul><h3
id="HowcanIgethelp-Alternativediscussionforums">Alternative discussion
forums</h3><p>There's a number of sites outside Apache that offer discussion
forums on Camel. For example, <a shape="rect" class="external-link"
href="http://stackoverflow.com/"; rel="nofollow">Stack Overflow</a> is a popular
Q & A site with a <a s
hape="rect" class="external-link"
href="http://stackoverflow.com/questions/tagged/apache-camel";
rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find
helpful discussions on technical blogs, on <a shape="rect"
class="external-link" href="https://www.google.com/search?q=apache+camel";
rel="nofollow">Google</a>, or even on <a shape="rect" class="external-link"
href="https://twitter.com/#!/search/apache%20camel";
rel="nofollow">Twitter</a>.</p><h3
id="HowcanIgethelp-Usingdeprecatedcomponents">Using deprecated
components</h3><p>Deprecated components are <strong>not</strong> supported
and issues such as bugs may not be fixed. We encourage users to migrate away
from using any deprecated component. A list of deprecated components is listed
on the github page at: <a shape="rect" class="external-link"
href="https://github.com/apache/camel/tree/master/components#components";
rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h
3 id="HowcanIgethelp-Howtogethelp">How to get help</h3><p>Before you report a
problem, you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br
clear="none"> When you report an issue, please be sure to include as much
information as possible. The more we know, the easier it is to reach an
effective solution quickly.</p><div class="confluence-information-macro
confluence-information-macro-note"><p class="title">What version do you
use</p><span class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>What version of Camel do you use!
Remember to include this information.</p></div></div><ul><li><strong>what are
the version numbers of involved software components?</strong> (this is very
important to detail)</li><li>what platform and JDK?</li><li>any particular
container being used? and if so, what version?</li><li>stack traces generally
really help! (<strong>Remember to post which version
of Camel you use, this is important to know when posting
stacktraces</strong>) 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.</li><li>log output
can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can
help</li><li>your code & configuration files are often useful</li><li>did
it work before? what have you changed to break it?</li><li>try upgrading to the
latest release and see if it's fixed there</li><li>try the latest SNAPSHOT to
see if it's fixed in the pre-release</li><li>search the user forum to see if
has been discussed before</li><li>see the "known issues" section in the release
notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue t
racker</a> to see if the issue has already been reported</li><li>do
<strong>not</strong> send private emails to Camel <a shape="rect"
href="team.html">Team</a> members to ask them to help you faster, or in the
private only. Help on Apache Camel is volunteer based and <strong>must</strong>
happen in the <strong>open</strong> on the public <a shape="rect"
href="mailing-lists.html">Mailing Lists</a>. If you want to get help
faster or in private, then see further below.</li></ul><h3
id="HowcanIgethelp-Howtogethelpfaster">How to get help faster</h3><p>We can
help you much quicker if you try the following</p><ul><li>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?</li><li><a shape="rect"
class="external-link" href="http://camel.apache.org/contributing.html";>submit a
patch</a> fixing the bug! (We also buy you beer when we meet you if you submit
bug fixes <img class="emoticon emotico
n-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak 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 it's huge) to the JIRA we can
normally fix things much faster. e.g. you could run <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html";
rel="nofollow">jmap</a>/<a shape="rect" class="external-link"
href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html";
rel="nofollow">jhat</a>, JProfiler or YourKit on your code and send us the
output. To find memory leaks it's quicker to resolve if you can tell us what
classes are taking up all of the RAM; we can normally figure out what's wrong
from that.</li></ul><h2 id="HowcanIgethelp-CommercialSupport">Commercial
Support</h2><p>This is an open sour
ce project, so the amount of time we have available to help resolve your issue
is often limited as all help is provided on a volunteer basis. If you want to
get priority help, need to get up to speed quickly, require some training or
mentoring, or need full 24 x 7 production support you could contact one of the
following companies with <a shape="rect"
href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/irc-room.html
==============================================================================
--- websites/production/camel/content/irc-room.html (original)
+++ websites/production/camel/content/irc-room.html Tue Jul 11 08:20:00 2017
@@ -75,7 +75,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="IRCRoom-IRC">IRC</h2><p>You can
hang out on IRC in the #apache-camel room at freenode with other Apache Camel
developers and users.</p><h3 id="IRCRoom-UsinganIRCclient">Using an IRC
client</h3><p>Here are the connection details. </p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>server</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>irc.freenode.net</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>port</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>6667</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>room</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>#apache-camel</p></td></tr></tbody></table></div><p> </p><p>IRC
logs are available at: <a shape="rect" class="external-link"
href="http://irclogs.dankulp.com/logs/irclogger_logs/apache-camel";
rel="nofollow">http://irclogs.dankul
p.com/logs/irclogger_logs/apache-camel</a></p><p>Older IRC logs until
2015-04-28 at: <a shape="rect" class="external-link"
href="http://irclogs.dankulp.com/logs/irclogger_logs/camel";
rel="nofollow">http://irclogs.dankulp.com/logs/irclogger_logs/camel</a></p></div>
+<div class="wiki-content maincontent"><h2 id="IRCRoom-IRC">IRC</h2><p>You can
hang out on IRC in the #apache-camel room at freenode with other Apache Camel
developers and users.</p><h3 id="IRCRoom-UsinganIRCclient">Using an IRC
client</h3><p>Here are the connection details. </p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>server</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>irc.freenode.net</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>port</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>6667</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>room</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>#apache-camel</p></td></tr></tbody></table></div><h2
id="IRCRoom-GitterRoom"><br clear="none">Gitter Room</h2><p>Apache Camel is
also on Gitter in the <a shape="rect" class="external-link"
href="https://gitter.im/apache/apache-camel"; rel=
"nofollow">apache/apache-camel</a> room which you can access from a web
browser.</p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/support.html
==============================================================================
--- websites/production/camel/content/support.html (original)
+++ websites/production/camel/content/support.html Tue Jul 11 08:20:00 2017
@@ -75,7 +75,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting
Help</h2><p>If you are experiencing problems using Camel then please report
your problem to our mailing list. This allows the entire community to help with
your problem. If indeed a bug has been identified in the Camel software, then
document the problem in our <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a>. Please
refrain from immediately opening a ticket in the issue tracker unless you are
certain it's a problem in the Camel software. If you are in doubt, we
appreciate asking the mailing list first.</p><div
class="confluence-information-macro confluence-information-macro-tip"><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Please read the section below
(<em>How to get help</em>), and follow the bullets advised there
first.</p></div></div><div c
lass="confluence-information-macro
confluence-information-macro-information"><p class="title">Reporting bugs -
Please read this first</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>We prefer people to get in touch
first using the mailing list. Or take time to read FAQs, or search in the
mailing list archives to find answers.<br clear="none"> Unfortunately some
people create a JIRA ticket as first thing. Please don't do that! Only if you
are sure it really is a bug etc. JIRA tickets create noise<br clear="none"> for
the Camel team to react on issues that are not bugs. But already covered in
FAQs, in the mailing lists etc. Or in the existing documentation.<br
clear="none"> Also on the mailing lists there is more people active to help you
better.</p></div></div><ul><li><a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a></li><li><a
shape="rect" href="faq.html">FAQ</a></li></ul><h3
id="Support-Alternativediscussionforums">Alternative discussion
forums</h3><p>There's a number of sites outside Apache that offer discussion
forums on Camel. For example, <a shape="rect" class="external-link"
href="http://stackoverflow.com/"; rel="nofollow">Stack Overflow</a> is a popular
Q & A site with a <a shape="rect" class="external-link"
href="http://stackoverflow.com/questions/tagged/apache-camel";
rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find
helpful discussions on technical blogs, on <a shape="rect"
class="external-link" href="https://www.google.com/search?q=apache+camel";
rel="nofollow">Google</a>, or even on <a shape="rect" class="external-link"
href="https://twitter.com/#!/search/apache%20camel";
rel="nofollow">Twitter</a>.</p><h3 id="Support-Usingdeprecatedcomponents">Using
deprecated components</h3><p>Deprecated components are
<strong>not</strong> supported and issues such a
s bugs may not be fixed. We encourage users to migrate away from using any
deprecated component. A list of deprecated components is listed on the github
page at: <a shape="rect" class="external-link"
href="https://github.com/apache/camel/tree/master/components#components";
rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3
id="Support-Howtogethelp">How to get help</h3><p>Before you report a problem,
you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br
clear="none"> When you report an issue, please be sure to include as much
information as possible. The more we know, the easier it is to reach an
effective solution quickly.</p><div class="confluence-information-macro
confluence-information-macro-note"><p class="title">What version do you
use</p><span class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>What version of Camel do you use
! Remember to include this information.</p></div></div><ul><li><strong>what
are the version numbers of involved software components?</strong> (this is very
important to detail)</li><li>what platform and JDK?</li><li>any particular
container being used? and if so, what version?</li><li>stack traces generally
really help! (<strong>Remember to post which version of Camel you use, this is
important to know when posting stacktraces</strong>) 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.</li><li>log output can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can
help</li><li>your code & configuration files are often useful</li><li>did
it work before? what have you changed to break it?</li><li>try upgrading to t
he latest release and see if it's fixed there</li><li>try the latest SNAPSHOT
to see if it's fixed in the pre-release</li><li>search the user forum to see if
has been discussed before</li><li>see the "known issues" section in the release
notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the issue has already been reported</li><li>do <strong>not</strong> send
private emails to Camel <a shape="rect" href="team.html">Team</a> members to
ask them to help you faster, or in the private only. Help on Apache Camel is
volunteer based and <strong>must</strong> happen in the <strong>open</strong>
on the public <a shape="rect" href="mailing-lists.html">Mailing
Lists</a>. If you want to get help faster or in private, then see further
below.</li></ul><h3 id="Support-Howtogethelpfaster">How to get help
faster</h3><p>We can help you much quicker if you try the
following</p><ul><li>provide us with a JU
nit 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?</li><li><a shape="rect"
class="external-link" href="http://camel.apache.org/contributing.html";>submit a
patch</a> fixing the bug! (We also buy you beer when we meet you if you submit
bug fixes <img class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak 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 it's huge) to the JIRA we can
normally fix things much faster. e.g. you could run <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html";
rel="nofollow">jmap</a>/<a shape="rect" class="external-link"
href="http://java.sun.com/javase/6/docs/technotes/tools/s
hare/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your code and
send us the output. To find memory leaks it's quicker to resolve if you can
tell us what classes are taking up all of the RAM; we can normally figure out
what's wrong from that.</li></ul><h2 id="Support-CommercialSupport">Commercial
Support</h2><p>This is an open source project, so the amount of time we have
available to help resolve your issue is often limited as all help is provided
on a volunteer basis. If you want to get priority help, need to get up to speed
quickly, require some training or mentoring, or need full 24 x 7 production
support you could contact one of the following companies with <a shape="rect"
href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div>
+<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting
Help</h2><p>If you are experiencing problems using Camel then please report
your problem to our mailing list. This allows the entire community to help with
your problem. If indeed a bug has been identified in the Camel software, then
document the problem in our <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a>. Please
refrain from immediately opening a ticket in the issue tracker unless you are
certain it's a problem in the Camel software. If you are in doubt, we
appreciate asking the <a shape="rect" class="external-link"
href="http://camel.apache.org/mailing-lists.html";>mailing list</a>, <a
shape="rect" class="external-link"
href="http://camel.apache.org/irc-room.html";>IRC chat</a>, or <a shape="rect"
class="external-link" href="https://gitter.im/apache/apache-camel";
rel="nofollow">Gitter chat</a> first.</p><div
class="confluence-information-macro confl
uence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Please read the section below
(<em>How to get help</em>), and follow the bullets advised there
first.</p></div></div><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Reporting bugs -
Please read this first</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>We prefer people to get in touch
first using the <a shape="rect" class="external-link"
href="http://camel.apache.org/mailing-lists.html";>mailing list</a>, <a
shape="rect" class="external-link"
href="http://camel.apache.org/irc-room.html";>IRC chat</a> or <a shape="rect"
class="external-link" href="https://gitter.im/apache/apache-camel";
rel="nofollow">Gitter chat</a>. Or take time to read FAQs, or search in th
e mailing list archives to find answers.<br clear="none"> Unfortunately some
people create a JIRA ticket as first thing. Please don't do that! Only if you
are sure it really is a bug etc. JIRA tickets create noise<br clear="none"> for
the Camel team to react on issues that are not bugs. But already covered in
FAQs, in the mailing lists etc. Or in the existing documentation.<br
clear="none"> Also on the mailing lists there is more people active to help you
better.</p></div></div><ul><li><a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>Issue Tracker</a></li><li><a
shape="rect" href="faq.html">FAQ</a></li></ul><h3
id="Support-Alternativediscussionforums">Alternative discussion
forums</h3><p>There's a number of sites outside Apache that offer discussion
forums on Camel. For example, <a shape="rect" class="external-link"
href="http://stackoverflow.com/"; rel="nofollow">Stack Overflow</a> is a popular
Q & A site with a <a shape="rect" cl
ass="external-link"
href="http://stackoverflow.com/questions/tagged/apache-camel";
rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find
helpful discussions on technical blogs, on <a shape="rect"
class="external-link" href="https://www.google.com/search?q=apache+camel";
rel="nofollow">Google</a>, or even on <a shape="rect" class="external-link"
href="https://twitter.com/#!/search/apache%20camel";
rel="nofollow">Twitter</a>.</p><h3 id="Support-Usingdeprecatedcomponents">Using
deprecated components</h3><p>Deprecated components are
<strong>not</strong> supported and issues such as bugs may not be fixed.
We encourage users to migrate away from using any deprecated component. A list
of deprecated components is listed on the github page at: <a shape="rect"
class="external-link"
href="https://github.com/apache/camel/tree/master/components#components";
rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3
id="Support-Howtoge
thelp">How to get help</h3><p>Before you report a problem, you may wish to
read the <a shape="rect" href="faq.html">FAQ</a>. <br clear="none"> When you
report an issue, please be sure to include as much information as possible. The
more we know, the easier it is to reach an effective solution quickly.</p><div
class="confluence-information-macro confluence-information-macro-note"><p
class="title">What version do you use</p><span class="aui-icon aui-icon-small
aui-iconfont-warning confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>What version of Camel do you use!
Remember to include this information.</p></div></div><ul><li><strong>what are
the version numbers of involved software components?</strong> (this is very
important to detail)</li><li>what platform and JDK?</li><li>any particular
container being used? and if so, what version?</li><li>stack traces generally
really help! (<strong>Remember to post which version of Camel you use, this is i
mportant to know when posting stacktraces</strong>) 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.</li><li>log output can be useful too; sometimes <a shape="rect"
href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can
help</li><li>your code & configuration files are often useful</li><li>did
it work before? what have you changed to break it?</li><li>try upgrading to the
latest release and see if it's fixed there</li><li>try the latest SNAPSHOT to
see if it's fixed in the pre-release</li><li>search the user forum to see if
has been discussed before</li><li>see the "known issues" section in the release
notes</li><li>and check the <a shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CAMEL";>issue tracker</a> to see if
the iss
ue has already been reported</li><li>do <strong>not</strong> send private
emails to Camel <a shape="rect" href="team.html">Team</a> members to ask them
to help you faster, or in the private only. Help on Apache Camel is volunteer
based and <strong>must</strong> happen in the <strong>open</strong> on the
public <a shape="rect" href="mailing-lists.html">Mailing Lists</a>. If you
want to get help faster or in private, then see further below.</li></ul><h3
id="Support-Howtogethelpfaster">How to get help faster</h3><p>We can help you
much quicker if you try the following</p><ul><li>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?</li><li><a shape="rect"
class="external-link" href="http://camel.apache.org/contributing.html";>submit a
patch</a> fixing the bug! (We also buy you beer when we meet you if you submit
bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.
org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png"
data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak 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 it's huge) to the JIRA we can
normally fix things much faster. e.g. you could run <a shape="rect"
class="external-link"
href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html";
rel="nofollow">jmap</a>/<a shape="rect" class="external-link"
href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html";
rel="nofollow">jhat</a>, JProfiler or YourKit on your code and send us the
output. To find memory leaks it's quicker to resolve if you can tell us what
classes are taking up all of the RAM; we can normally figure out what's wrong
from that.</li></ul><h2 id="Support-CommercialSupport">Commercial
Support</h2><p>This is an open source project, so the amount of time we have
available to help resolve your issue is often limited as all help is provided
on a volunteer basis. If you want to get priority help, need to get up to speed
quickly, require some training or mentoring, or need full 24 x 7 production
support you could contact one of the following companies with <a shape="rect"
href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div>
</td>
<td valign="top">
<div class="navigation">
![https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png"](https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png"){kind=link}