You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Some of our customers doesn’t get the email that we send out from our servicedesk, however we can confirm that other customers do and when we send out a test mail it works without any issues.
When looking through the maillog (atlassian-jira-outgoing-mail.log) on our Jira-server we noticed that no new entries had been made since we upgraded Jira to the latest version. And every entry since then only said:
2022-01-25 22:22:15,896+0100 INFO  Caesium-1-2 [c.a.m.o.c.a.j.p.i.batching.cron.MemorySafeEventRetriever] Searching for scheduled events to notify and using queryTimeout of null seconds.
Do anyone recognize this message? As of now we don’t if this is an issue or not, because some users do receive emails that we send out, so it might be an error on the receiving side. But it’s interesting that the log haven’t really shown any kind of error message since we updated Jira.
I met on the Jira 8.20.14.
Finally, I disabled the batching functionality
I have spoken with Atlassian support and they told me that the logs are normal behaviour...
The package should be com.atlassian.mail.outgoing.com.atlassian.jira.plugins.inform.batching.cron
This log is in atlassian-jira-outgoing-mail.log
It seems normal. The 'null' value represent an optional Jira property you can set (com.atlassian.jira.plugins.inform.batching-plugin.queryTimeout).
Hi @Maxime Boyer ,
com.atlassian.mail.outgoing.com.atlassian.jira.plugins.inform.batching.cron to WARN works great. This annoying message has disappeared.
Which would be the default/recommended value for property com.atlassian.jira.plugins.inform.batching-plugin.queryTimeout?
I have the exact same issue for one of my customers