MailJobRunner Failed java.lang.IllegalStateException in e-mail log

[Thomas Uber]

Hi,

in our Jira log File (atlassian-jira-incoming-mail.log) i have some errors if there are mails imported:

Caesium-1-4 ServiceRunner MailJobRunner Failed
java.lang.IllegalStateException: Connection accessed outside the scope of a callback passed to com.atlassian.sal.api.rdbms.TransactionalExecutor

And after this ther is:

Caesium-1-2 ServiceRunner MailJobRunner Failed
java.lang.NoSuchMethodError: com.atlassian.sal.api.rdbms.TransactionalExecutor.getSchemaName()Lcom/atlassian/fugue/Option;

But all Mails are imported correctly. We Use "Jira Email this Issue" with Jira 8.2.3 to handle the incoming mails. 

Any Idea what these error messages mean?

Thanks

Thomas

[Eric Salonen]

Hi,

Looks like the problem is caused by a file called

jira-email-processor-plugin-2.7.1.jar

We had the following errors occuring in the logs:

2020-11-27 19:24:08,729+0200 ERROR [] Caesium-1-4 ServiceRunner     MailJobRunner Failed
java.lang.IllegalStateException: Connection accessed outside the scope of a callback passed to com.atlassian.sal.api.rdbms.TransactionalExecutor    at com.atlassian.sal.core.rdbms.WrappedConnection.connection(WrappedConnection.java:62) [?:?]    at com.atlassian.sal.core.rdbms.WrappedConnection.getMetaData(WrappedConnection.java:195) [?:?]    at com.atlassian.pocketknife.internal.querydsl.dialect.DefaultDialectConfiguration.buildTemplates(DefaultDialectConfiguration.java:111) [jira-email-processor-plugin-2.7.1.jar:?]    at com.atlassian.pocketknife.internal.querydsl.dialect.DefaultDialectConfiguration.detect(DefaultDialectConfiguration.java:72) [jira-email-processor-plugin-2.7.1.jar:?]

So if you have the same file (maybe a different version) installed in your installed-plugin folder it means that you have most likely had Jira Service Desk installed at some point.

As you can see, we also had the same error occurring:

2020-11-25 21:09:49,176+0200 ERROR [] Caesium-1-3 ServiceRunner MailJobRunner Failed
java.lang.NoSuchMethodError: com.atlassian.sal.api.rdbms.TransactionalExecutor.getSchemaName()Lcom/atlassian/fugue/Option;
at com.atlassian.pocketknife.internal.querydsl.schema.ProductSchemaProvider.getProductSchema(ProductSchemaProvider.java:26) [jira-email-processor-plugin-2.7.1.jar:?]
at com.atlassian.pocketknife.internal.querydsl.schema.DefaultSchemaProvider.getProductSchema(DefaultSchemaProvider.java:64) [jira-email-processor-plugin-2.7.1.jar:?]
at com.atlassian.pocketknife.internal.querydsl.dialect.DefaultDialectConfiguration.enrich(DefaultDialectConfiguration.java:80) [jira-email-processor-plugin-2.7.1.jar:?]

We uninstalled Jira Service Desk a long time ago and yet today, we found this file in the installed-plugins folder. This jar file belongs to Jira Service Desk and should most likely be removed if you no longer have Jira Service Desk installed in your Jira app.

As soon as we removed this file and restarted, the errors no longer occurred.

More information here:

https://confluence.atlassian.com/jirakb/unable-to-create-issue-by-e-mail-jira-email-processor-plugin-747609822.html

[Jozef Kotlár]

This bug is indication, that SAL component in Jira 8.x is upgraded to version 4.0.0 with changed API (com.atlassian.fugue replaced with io.atlassian.fugue). Probably this functionality is not used in JETI for your use case. You should contact add-on vendor.

There is rather obsolete SAL Version Matrix

[Ramesh Udari1]

How did you solve this issue ?

[Thomas Uber]

I didn't solve it. It is working correctly. But the error messages still remain.