Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

After Jira update 8.20.4, our maillog is filled with strange text string.

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

5 answers

Did you get a resolution?

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 18, 2022

I met on the Jira 8.20.14. 

Finally, I disabled the batching functionality

0 votes
Mathis Hellensberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 03, 2022

I have spoken with Atlassian support and they told me that the logs are normal behaviour...

Well, I guess that's fine, until you actually need to find something useful from the logs... 

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

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).

Like Rafael Corredor likes this

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

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.

0 votes
Mathis Hellensberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 23, 2022

I have the exact same issue for one of my customers

Did you get a resolution?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events