Closed SimonMachine closed 1 year ago
Hi @SimonMachine thank you for the callout, I can reproduce the error.
According to the service model, the timestamp should be iso8601
:
and the service is sending 1.655421227201E9
in the response.
And the "timestampFormat":"iso8601"
trait was added to the model in Feb 2019, probably to fix the previous issue - https://github.com/aws/aws-sdk-java-v2/issues/1053.
I'll reach out to the DLM service team.
The DLM is investigating the root cause.
Since this is an issue on the service side, it may impact other SDKs, so I'm transferring this to the aws-sdk
repo for visibility.
I'll update here with any new info.
hello,team, is there any update for this issue ?
@SimonMachine the DLM team released a fix, getLifecyclePolicy
should be working now. Please check it out and let us know of any further question.
"Policy": {
"PolicyId": "policy-xxx",
"Description": "My policy test",
"State": "DISABLED",
"StatusMessage": "DISABLED",
"ExecutionRoleArn": xxx,
"DateCreated": "2023-03-27T21:43:40.716000+00:00",
"DateModified": "2023-03-27T21:43:40.782000+00:00",
...
This issue is now closed.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
When trying to get a snapshot lifecycle policy using the ''dlmClient' and 'getLifecyclePolicy' method, get an unexpected exception regarding date parse.
Expected Behavior
dlmClient can parse the timestamp and get the policy object.
Current Behavior
error log: Unable to unmarshall response (Text '1.655421227201E9' could not be parsed at index 0). Response Code: 200, Response Text: OK
('1655421227.201E9' is the time when I created the dlm policy. )
Reproduction Steps
Create a Snapshot lifecycle policy from the aws console. Use the aws java sdk to fetch it using the getLifecyclePolicy method.
Possible Solution
No response
Additional Information/Context
similar issue: 1053
AWS Java SDK version used
2.20.28
JDK version used
corretto-17.0.6
Operating System and version
windows server 2019