The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JETI exception while processing an incoming email

Ganesh Oak
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2015

I get the below message when I try to configure Email This Issue Mail Handler for a project/issue type combination for which I've defined a mail handler. What could be the cause of this error? What am I doing wrong?

JIRA 6 / JETI 5.4.1

Exception: key should not be null!: key should not be null!

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Sergey Egorov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 15, 2016

+1 - we have the same issue.

Perfect error reporting! :-/

0 votes
Juan P Gomez
October 5, 2015

In our company we are having the same issue. 2015-09-22 15:31:01,537 atlassian-scheduler-quartz1.clustered_Worker-2 ERROR anonymous ECS Mail Handler [atlassian.mail.incoming.mailfetcherservice] ECS Mail Handler[10040]: Exception: key should not be null! com.atlassian.jira.util.dbc.Assertions$NullArgumentException: key should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29) Have you been able to fix the error? JIRA 6.4.8 / JETI 6.3.0.2