There is some impact, but unless your system is send vast amounts of email, it's not enough to worry about if you're only going to have it on for a short debugging session (I'd turn it off after 10 minutes, should be long enough to find the problem)
We are having a problem of being slow when sending email notifications sometimes. Also in the log files we can see sometimes java.net.SocketTimeoutException: Read timed out. That's why we are going to enable the debug mode and see according to the https://confluence.atlassian.com/jirakb/notification-mail-slow-to-arrive-or-having-huge-delay-397803670.html
Ok, the additional logging you suggest is probably going to make this problem noticably worse while it is enabled but it is very worth it for the debugging information you will get.
However. When you get "java.net.SocketTimeoutException: Read timed out." that really does mean that the JIRA server cannot connect to the email server to hand it any mail. The JIRA logs will probably confirm that, and then the problem becomes one of networking, not JIRA.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs