Library fails while constructing ErrorResponse

[simonedavico]

I was trying to contact my Minio instance specifying a wrong address earlier, and it seems like error reporting is broken. ErrorResponse.parseXml throws some exception about the xml being malformed.

Stack trace:

! org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not 4 (position: START_DOCUMENT seen 4... @1:1) 
! at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1519) ~[xpp3-1.1.4c.jar:na]
! at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395) ~[xpp3-1.1.4c.jar:na]
! at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) ~[xpp3-1.1.4c.jar:na]
! at com.google.api.client.xml.Xml.parseElementInternal(Xml.java:245) ~[google-http-client-xml-1.20.0.jar:1.20.0]
! at com.google.api.client.xml.Xml.parseElement(Xml.java:222) ~[google-http-client-xml-1.20.0.jar:1.20.0]
! at io.minio.messages.XmlEntity.parseXml(XmlEntity.java:62) ~[minio-1.0.1.jar:1.0.1]
! at io.minio.messages.ErrorResponse.parseXml(ErrorResponse.java:134) ~[minio-1.0.1.jar:1.0.1]
! at io.minio.messages.ErrorResponse.<init>(ErrorResponse.java:60) ~[minio-1.0.1.jar:1.0.1]
! at io.minio.MinioClient.execute(MinioClient.java:522) ~[minio-1.0.1.jar:1.0.1]
! at io.minio.MinioClient.executeGet(MinioClient.java:635) ~[minio-1.0.1.jar:1.0.1]
! at io.minio.MinioClient.getObject(MinioClient.java:836) ~[minio-1.0.1.jar:1.0.1]
! at io.minio.MinioClient.getObject(MinioClient.java:769) ~[minio-1.0.1.jar:1.0.1]

[balamurugana]

! at io.minio.MinioClient.execute(MinioClient.java:522) ~[minio-1.0.1.jar:1.0.1]

I see errorResponse = new ErrorResponse(new StringReader(errorXml)); fails due to wrong xml format/content from http body.

Is it possible to provide what http body content it got?

[simonedavico]

Of course, if you can suggest me how to retrieve it. minio-java doesn't implement any kind of logging, right?

[harshavardhana]

Of course, if you can suggest me how to retrieve it. minio-java doesn't implement any kind of logging, right?

@simonedavico - there is way, just enable s3Client.traceOn(stream) it would log all the request and response headers.

[simonedavico]

Thank you! I will investigate the issue ASAP and report here.

[harshavardhana]

Thank you! I will investigate the issue ASAP and report here.

Checking back on this were you able to investigate this further?

[simonedavico]

Sorry, not yet. I've been very busy with my thesis in the last few months, and completely forgot about the issue. I will try to do it in the next few days.

[harshavardhana]

Sorry, not yet. I've been very busy with my thesis in the last few months, and completely forgot about the issue. I will try to do it in the next few days.

No problem @simonedavico, all the best on your thesis :-)

[harshavardhana]

Closing this since there hasn't been any update, please re-open if it happens again.