Invalid XML payload sent by client: Unexpected attributes found for DOM element Object: {zdef1777600993:length=11}\

53 views
Skip to first unread message

Vladyslav Kopaniev

unread,
Jun 14, 2023, 2:54:07 AM6/14/23
to Spectra Logic S3 SDKs, APIs, and RioBroker
Hi we are getting a weird error when trying to start read jobs in out QA environment. Please see the details below:

SDK: "com.github.spectralogic:ds3_java_sdk:5.4.0"
Error message: "Expected a status code of 200 but got 400 for request #8289854. Error message: \"BadRequest[400]: Invalid XML payload sent by client: Unexpected attributes found for DOM element Object: {zdef1777600993:length=11}\" "

The error message arises when we attempt to execute method Ds3ClientHelpers#startReadJob(final String bucket, final Iterable<Ds3Object> objectsToRead). Please, see the full stack trace in the attachments.
Please note that we have tried other API calls like the "listObjects" method and they returned as expected.

Please help us understand why this issue is happening and what could be the fix here.
stacktrace.txt

George Trossell

unread,
Jun 14, 2023, 3:12:17 PM6/14/23
to Spectra Logic S3 SDKs, APIs, and RioBroker

Hi Vladyslav Kopaniev

Which SDK and version are you using ?

George

Vladyslav Kopaniev

unread,
Jun 15, 2023, 3:28:54 AM6/15/23
to Spectra Logic S3 SDKs, APIs, and RioBroker
We are using java sdk of version 5.4.0

George Trossell

unread,
Jun 15, 2023, 6:13:24 AM6/15/23
to Spectra Logic S3 SDKs, APIs, and RioBroker
If you are using BlackPearl OS version 5.6.0, you will need to upgrade to SDK version 5.6.0 as we found a flag was missing in the 5.4.0 build. 

If you are not using BP OS version 5.6.0, can you please let me know what version you are using.

Thanks 

Vladyslav Kopaniev

unread,
Jun 15, 2023, 10:08:10 AM6/15/23
to Spectra Logic S3 SDKs, APIs, and RioBroker
Currently we are using OS version 

 5.5.2

If I change the version of the java SDK from 5.4.0 (current) to 5.6.0 I will see a different error:
"Provider for javax.xml.stream.XMLInputFactory cannot be found", which is more likely a client's runtime error, I can send you a full stacktrace of that if needed.
Reply all
Reply to author
Forward
0 new messages