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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Received an invalid cluster message to invalidate user

We upgraded from JIRA Software 7.1.1 to JIRA DataCenter 7.3.3 and now every so often we see an odd message in the logs.  I have not been able to track it down.  It seems to happen right around the time we are synchronizing with Active Directory.  

Has anyone else seen an error message like this in JIRA and if so, how did you resolve it?

ClusterMessageHandlerServiceThread:thread-1 ERROR [c.a.j.c.embedded.ofbiz.IndexedUserDao] Received an invalid cluster message to invalidate user:
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(
at java.lang.Long.parseLong(
at java.lang.Long.parseLong(
at com.atlassian.jira.crowd.embedded.ofbiz.IndexedUserDao$InvalidationClusterMessageConsumer.receive(
at com.atlassian.jira.cluster.OfBizMessageHandlerService.sendLocalFromNode(
at com.atlassian.jira.cluster.OfBizMessageHandlerService.handleReceivedMessages(
at com.atlassian.jira.cluster.OfBizMessageHandlerService.access$000(
at com.atlassian.jira.cluster.OfBizMessageHandlerService$
at java.util.concurrent.Executors$
at java.util.concurrent.FutureTask.runAndReset(
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

2 answers

Suggest an answer

Log in or Sign up to answer

We have the same issue and I would like to ask if you have got any kind of resolution from the Atlassian support team? 

Please let me know how you have resolved this issue.


Thank You!

The case went stale because of priorities.  We were not able to tie the error message to any user issue and it dropped like a rock to the bottom of my queue. I still see this issue after upgrading to Jira 7.4.2  When things calm down after I finish my current project load, I may be able to send Atlassian a scrubbed copy of our database for review.

My guess is that it is caused by 1 or more of the following:

  1. multiple domains being synched
  2. multiple domain controllers for each domain
  3. being configured to hit the domain instead of the Atlassian recommended FQDN of a single domain controller (because who needs redundancy?)
  4. multiple Jira directories synching the 
  5. a misbehaving domain controller

Are any of the items similar in your environment?

I am getting the same error. I guess it is due to user account conflicts. I had a local user with same email ID as my external user directory. But can't figure out to clear this error.


Tried few things by updating email address and name etc. But no luck

We are also getting the same error.

We have the same error for Jira 8.5.3

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 22, 2017

I understand you are working with the JIRA support team to resolve this on I look forward to hearing the result of the investigation.

AUG Leaders

Atlassian Community Events