[NETCONF-270] 2 digits milliseconds can not be parsed in notification eventTime Created: 06/Sep/16  Updated: 15/Mar/19  Resolved: 07/Mar/17

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Hou Jin Assignee: Miroslav Kovac
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

Issue Links:
Blocks
is blocked by MDSAL-206 DOMEvent contains only event time wit... Resolved
External issue ID: 6645

 Description   

When I use netconf to recevice and process our device's notification, I
found that the EvnetTime cound not be parsed.

The EventTinme is like:

?eventTime?2016-09-05T07:11:39.18Z?/eventTime?

But the controller throw an expection:

Unable to parse event time from XmlElement

{name='eventTime', namespace='urn:ietf:params:xml:ns:netconf:notification:1.0'}

. Setting time
to Thu Jan 01 08:00:00 CST 1970
java.text.ParseException: Unparseable date: "2016-09-05T07:11:39.18Z"
at java.text.DateFormat.parse(DateFormat.java:357)
at
org.opendaylight.controller.sal.connect.netconf.schema.mapping.NetconfMessageTransformer$3$1.parse(NetconfMessageTransformer.java:157)

I find that when the 2 digits milliseconds can not be parsed and 6 digits
milliseconds can be parsed.

 Comments   
Comment by Alexis de Talhouët [ 18/Nov/16 ]

https://git.opendaylight.org/gerrit/#/c/48495/

Generated at Wed Feb 07 20:14:35 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.