Lots of IllegalFormatConversionException in greenhopper.log

[Christian Becker]

Hi,

while investigating some issues with our installation we've found a lot of entries in greenhopper.log like these:

2020-01-08 07:34:55,573 http-nio-8080-exec-5 ERROR user1 454x979437x2 u40z7a 10.15.16.141,127.0.0.1 /rest/greenhopper/1.0/xboard/config.json [service.rapid.view.ColumnServiceImpl] Unable to format message: Invalid status [id %d] mapped to column [id %d], ignoringjava.util.IllegalFormatConversionException: d != java.lang.String

2020-01-07 16:24:18,193 http-nio-8080-exec-7 ERROR user2 984x977113x1 5g6ybo 10.128.233.81,127.0.0.1 /secure/RapidBoard.jspa [service.rapid.view.ColumnServiceImpl] Unable to format message: Invalid status [id %d] mapped to column [id %d], ignoringjava.util.IllegalFormatConversionException: d != java.lang.String

2020-01-07 08:42:51,752 http-nio-8080-exec-4 ERROR public 522x968784x1 13v1oz7 10.12.0.48,127.0.0.1 /rest/agile/1.0/board/139/sprint [service.rapid.view.ColumnServiceImpl] Unable to format message: Invalid status [id %d] mapped to column [id %d], ignoringjava.util.IllegalFormatConversionException: d != java.lang.String

Any ideas where they come from and how to solve this issue?

Bests
Chris

[Andy Heinzer]

Hi Christian,

This particular error indicates that you have at least one board in Jira that is setup with a status in a column that appears to be an invalid status (or perhaps the name of the status has some kind of illegal character in the name).  I'm not certain exactly what is causing this just yet, I have a few theories about what might be the source here.

Try going to the board with the id of 139, or more precisely, try the URL /secure/RapidBoard.jspa?rapidView=139

Does this board load without error to the browser?  It might help to check the browser console to see if there is by chance an error or warning message getting tossed into the browser console log when loading this board.

I'd then go into the Board -> Configure Board page.  Check the Columns section here.  This will tell you what statuses are setup to appear in each column.  I would be interested to see what status values exist here.  Perhaps if we can take a look at both the $JIRAHOME/log/atlassian-jira.log at this time, as well as the browser console when loading these pages, perhaps we can learn the ID of the status to then lookup against the SQL database here.

It's possible that something is corrupted in your Jira database.  You might also take a look at using the database integrity checker.  Sometimes it can locate problems like this and either correct them or give you more details about the source problem here.

Please let me know the results.

Andy