[#PERF-116] Error parsing mod time string

Perforce JIRA plugin

Error parsing mod time string

Created: 20/Mar/07 10:49 AM Updated: 29/Mar/07 09:34 PM

Component/s:

None

Affects Version/s:

1.1.9

Fix Version/s:

1.1.10

Time Tracking:

Not Specified

Environment:

using Jira 3.8

Participants:	Daniel Woodhams, Dylan Etkin [Atlassian] and Jed Wesley-Smith [Atlassian]
Since last comment:	1 year, 27 weeks, 3 days ago
Resolution Date:	29/Mar/07 09:34 PM
Labels:

Description

« Hide

The plugin has problems parsing the date string but is still working - we have just upgrade our Jira and the p4 plugin and are now seeing this error in the logs. fyi - We also are running the latest version of java which includes the day light savings patch.

2007-03-20 11:28:21,439 JiraQuartzScheduler_Worker-0 ERROR [plugin.ext.perforce.PerforceUtils] Error parsing mod time string: 2007/03/20

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jed Wesley-Smith [Atlassian] added a comment - 25/Mar/07 07:50 PM

For some reason you are not getting passed the time portion. The PerforceUtils expects a time string that contains the HH:MM:SS portion to be specified and does not cope when this is left out.

Unfortunately I cannot think of a reason this is no longer being passed. Could you please verify which version of the atlassian-p4package jar you are using?

[ Permlink | « Hide ]

Dylan Etkin [Atlassian] added a comment - 28/Mar/07 01:39 AM

I have verified that we are seeing this same error message in the logs for the nightly functional tests we run for this. It looks like there are two places where this could cause null pointer exceptions, the P4ChangeAction and P4JobAction constructors. In terms of indexing this just means we are not indexing that date.

[ Permlink | « Hide ]

Jed Wesley-Smith [Atlassian] added a comment - 29/Mar/07 09:34 PM

Now properly parses and indexes yyyy/MM/dd dates (without time string)