Details
-
Bug
-
Resolution: Fixed
-
Highest
-
55
-
Severity 1 - Critical
-
40
-
Description
NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.
Summary
When generation a backup, it fails with:
2016-12-01 08:48:13.581535500 Caused by: com.atlassian.rdbms.dbimportexport.dbie.api.datafile.DatafileParseException: Could not parse timestamp '2016-10-17 11:59:46.178' with pattern '(ParseCaseSensitive(false)Value(YearOfEra,4,10,NEVER)'-'Value(MonthOfYear,2)'-'Value(DayOfMonth,2))' '(Value(HourOfDay,2)':'Value(MinuteOfHour,2)':'Value(SecondOfMinute,2)[Fraction(MicroOfSecond,0,6,DecimalPoint)])[Offset(+HH:MM:SS,'+00')][Offset(+HH:MM,'+00')][Offset(+HH,'+00')]Text(Era)'
The backup fails to parse the date in the AO table:
"AO_6D345F_CUSTOM_LIBRARY"
Which holds custom libraries from Gliffy.
Enviroment
Confluence Cloud = 1000.607.0
Steps to Reproduce
- Generate a backup through the Backup Manager
Expected Results
Backup gets created successfully.
Actual Results
Backups fails with:
Export error Unsupported field: InstantSeconds But don't worry, we'll fix it for you! You just need to contact Atlassian support and paste in this error message, timestamp and your instance details. Timestamp: 2016-11-30T09:47:56.132-08:00
Workaround
There are two workarounds:
- Wait until roughly the end of January, when we are migrating to a new version of Gliffy. After this, it should work again. Note that the new version of Gliffy does not support the import/export of custom shape libraries.
- - OR -
- Contact support who will run the Gliffy data fix script. (attached to ticket)
Attachments
Issue Links
- is related to
-
CONFSERVER-45477 Backup creation fails with "Could not parse timestamp" error
- Closed