It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Received an invalid cluster message to invalidate user

Matthew Harkins Apr 05, 2017

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

0 votes
Ann Worley Atlassian Team 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.

0 votes
invinci Sep 29, 2017

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!

Matthew Harkins Sep 29, 2017

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?

Mendus Chelapurath Jan 30, 2018

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

Christian Lund Jun 15, 2018

We are also getting the same error.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Data Center

Two free email courses to help you “level up” your enterprise strategy

  Hey Atlassian Community! Scaling. Growth. Innovation. These are topics that play on repeat for any enterprise organization. As your organization grows and tools become increasingly mission-c...

181 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you