Users are unable to send email via JETI Plug-in and getting blank email while sending it

[Jose Aguilera]

General information:
We are using the plugin e-mail this issue (version 7.1.1.5 - https://marketplace.atlassian.com/apps/4977/email-this-issue?hosting=server&tab=overview\); our JIRA Software version is 7.7.1. 

Description of the issue:
Yesterday our instances crashed two times. We saw a sudden increase in the load average on our Ubuntu machine (from under 1 to 12). In the logs, we saw several messages like this:

2018-09-26 21:53:02,088 Thread-34 WARN anonymous [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=0; marks=[-1-0]; pool=13/20

So, we decided to increase the pool size to 35 (all the values were changed from 20 to 35 in the DB config file). After that, we restarted the instance. It has been working fine since then, however today I was told by the customers that they are unable to send e-mails via the JETI plugin; they are getting a blank e-mail. If we try to see the preview of the message, we get an exception below:

Also, I have pasted below the content of the log related to this issue. Besides the pool size change and the restart of the instance, no changes have been made.

/rest/jeti/1.0/email [c.m.j.p.emailissue.template.TemplateRendererImpl] Exception getting message body from Velocity: org.apache.velocity.exception.VelocityException: An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.

Details:
-------
java.lang.NullPointerException
at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:1102)
at org.apache.velocity.runtime.RuntimeInstance.parse(RuntimeInstance.java:1085)
at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1198)
at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1164)
at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:219)
at com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:205)
at com.metainf.jira.plugin.emailissue.template.TemplateRendererImpl.renderContent(TemplateRendererImpl.java:60)
at com.metainf.jira.plugin.emailissue.template.TemplateRendererImpl.renderContent(TemplateRendererImpl.java:43)
at com.metainf.jira.plugin.emailissue.template.TemplateRendererImpl.renderTextContent(TemplateRendererImpl.java:34)
at com.metainf.jira.plugin.emailissue.action.EmailBuilderImpl.buildEmail(EmailBuilderImpl.java:1061)
at com.metainf.jira.plugin.emailissue.action.EmailBuilderImpl.sendEmailWithUserEditedSubject(EmailBuilderImpl.java:292)
at com.metainf.jira.plugin.emailissue.action.EmailBuilderImpl.sendEmail(EmailBuilderImpl.java:779)
at com.metainf.jira.plugin.emailissue.mail.EmailSenderImpl$1.execute(EmailSenderImpl.java:55)
at com.metainf.jira.plugin.emailissue.mail.AsynEmailSender.run(AsynEmailSender.java:31)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

[Matthew Harkins]

Just adding a similar experience.  We upgraded the scriptrunner plugin on our datacenter instance this last weekend and something went sideways on one of our nodes.  When this particular node tried sending email from a JETI Event notification, it would fail with a similar stack trace (see below).  We didn't see the empty emails you described, but the notification emails were never sent.  After a restart of the node, the plugins appear to have sorted out their differences and are functioning normally again.

ERROR: Bundle com.onresolve.jira.groovy.groovyrunner [202] Unable to get module class path. (java.lang.NullPointerException)
java.lang.NullPointerException
at org.apache.felix.framework.BundleRevisionImpl.calculateContentPath(BundleRevisionImpl.java:431)
at org.apache.felix.framework.BundleRevisionImpl.initializeContentPath(BundleRevisionImpl.java:368)
at org.apache.felix.framework.BundleRevisionImpl.getContentPath(BundleRevisionImpl.java:354)
at org.apache.felix.framework.BundleRevisionImpl.getResourceLocal(BundleRevisionImpl.java:493)
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1505)
at org.apache.felix.framework.BundleWiringImpl.getResourceByDelegation(BundleWiringImpl.java:1417)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.getResource(BundleWiringImpl.java:2419)
at com.atlassian.core.util.ClassLoaderUtils.getResource(ClassLoaderUtils.java:104)
at com.atlassian.core.util.ClassLoaderUtils.getResourceAsStream(ClassLoaderUtils.java:180)
at com.metainf.jira.plugin.emailissue.util.FileUtils.resolveFile(FileUtils.java:51)
at com.metainf.jira.plugin.emailissue.util.FileUtils.readFile(FileUtils.java:45)
at com.metainf.jira.plugin.emailissue.template.TemplateRendererImpl.renderContent(TemplateRendererImpl.java:54)
at com.metainf.jira.plugin.emailissue.template.TemplateRendererImpl.renderContent(TemplateRendererImpl.java:43)
at com.metainf.jira.plugin.emailissue.action.EmailBuilderImpl.buildEmail(EmailBuilderImpl.java:1024)
at com.metainf.jira.plugin.emailissue.action.EmailBuilderImpl.sendEmailWithUserEditedSubject(EmailBuilderImpl.java:290)
at com.metainf.jira.plugin.emailissue.action.EmailBuilderImpl.sendEmail(EmailBuilderImpl.java:779)
at com.metainf.jira.plugin.emailissue.mail.EmailSenderImpl$1.execute(EmailSenderImpl.java:56)
at com.metainf.jira.plugin.emailissue.mail.AsynEmailSender.run(AsynEmailSender.java:34)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

[Jose Aguilera]

Here is an update. We disabled the add-on and then enabled it again. After that, the issue described was gone. Posting the "solution" here in case someone experiences the same. I will update the thread once we hear from the vendor.