"time too early" errors on reindex: Due date field not checked for sanity when creating/editing issues

When creating or updating an issue, a completely bogus date, such as 0035-01-24) can be entered. In the CreateIssue page, this results in an indexing exception. In the Update page, it lets this bogus date through. Then when an admin tries to reindex the data, the reindex dies with an error:

1. Exception reindexing: com.atlassian.jira.issue.index.IndexException: Error: java.lang.RuntimeException: time too early: time too early

And in the stdout logs (logs/catalina.out):
WARN [jira.issue.index.DefaultIndexManager] There was an exception whilst reindexing issue XYZ-291java.lang.RuntimeException: time too early

Fortunately the stdout logs (to logs/catalina.out) contain the affected key (XYZ-291 above). The workaround is to fix the due date in the database. This can be done by either:

• Create an XML export (backup) of the database
• Edit the XML, search for something like:

<Issue assignee="jsmith" created="2003-08-22 23:16:47.0" duedate="0035-01-24 00:00:00.0" ...

Fix the duedate attribute, and import the XML.

Or:

• In the database, run the query:

update jiraissue set duedate='2004-01-24 00:00:00.0' where pkey='XYZ-291';