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.
Thank you
I met on the Jira 8.20.14.
Finally, I disabled the batching functionality
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have spoken with Atlassian support and they told me that the logs are normal behaviour...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, I guess that's fine, until you actually need to find something useful from the logs...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Any news about it? We have recently upgraded to v8.20.6 and it is the same case. I assume it is possible to configure a logging package to WARN level to make sure those messages are not logged. The question is... which one?
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad it worked for you. I wouldn't change that setting. I guess you could set it to a few seconds if you really wanted to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the exact same issue for one of my customers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.