Viewing Project Summary Versions result in Exception

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Viewing a specific version in Project Summary results in an error:

  • Dashboard > Project > selected project > Versions > selected version

The following appears in the atlassian-jira.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 2013-05-09 13:27:35,694 http-bio-8080-exec-14 ERROR admin 807x21889x1 fp00y9 10.60.0.102 /browse/TEST/fixforversion/10800 [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.ArithmeticException: Value cannot fit in an int: 26845333735 java.lang.ArithmeticException: Value cannot fit in an int: 26845333735 at org.joda.time.field.FieldUtils.safeToInt(FieldUtils.java:187) at org.joda.time.field.BaseDurationField.getDifference(BaseDurationField.java:141) at org.joda.time.Days.daysBetween(Days.java:137) at com.atlassian.jira.datetime.AbstractDateTimeRelativeDatesFormatter$RelativeFormatter.getDayI18nKey(AbstractDateTimeRelativeDatesFormatter.java:104) at com.atlassian.jira.datetime.AbstractDateTimeRelativeDatesFormatter.format(AbstractDateTimeRelativeDatesFormatter.java:58) at com.atlassian.jira.datetime.DateTimeFormatterImpl.format(DateTimeFormatterImpl.java:48) at sun.reflect.GeneratedMethodAccessor2674.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:381) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:370) at com.atlassian.velocity.htmlsafe.introspection.UnboxingMethod.invoke(UnboxingMethod.java:30) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)

Cause

A stored date within the index has been improperly stored, resulting in a arithmetic exception when JIRA attempts to calculate the date.

Resolution

  • Run a re-index on your JIRA system

  • JIRA Administration > System > Advanced > Indexing

    ℹ️ For JIRA 5.2+ ensure that you use the "Lock JIRA and rebuild index" option.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.