Occasional SAXParseException about sbt-sonatype HOT 21 CLOSED

sbt-sonatype 3.9.1 has switched to JSON based API, so this error will no longer happen. Thanks.

from sbt-sonatype.

Right now, I would say this is occassional always. We've been experiencing the same kind of behavior for the past few days.

from sbt-sonatype.

It looks like Sonatype is returning HTML response, instead of XML.. Weird...

from sbt-sonatype.

I guess there may be an error HTTP status

from sbt-sonatype.

HTTP status code (200) is checked here, so after that XML (or html) will be parsed.

from sbt-sonatype.

This bug report is a POST request.

It seems that only 500 error status is checked for POST status.

from sbt-sonatype.

Nice catch! Then we need to have more proper status code handling here.

from sbt-sonatype.

hi - have been hit by the same issue, using sbt-sonatype 3.8. is there a temporary workaround? this is blocking some important release on our side.

just retrying... 😅

from sbt-sonatype.

Right. Sonatype sometimes returns HTML responses for XML request.

I'm thinking about switching to JSON based APIs and adding more retries around the parsing errors.

from sbt-sonatype.

imo Sonatype should fix this, you do everything right. I've been trying to publish an artefact for 6 hours and it's failing all the time 🤦‍♂

from sbt-sonatype.

Judging from Sonatype's issue tracker (https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-52239?filter=allopenissues) I would say that this SAXParserException is just because we are getting socket timeouts in a form of automatic HTML failure responses. the plugin should probably still recognize it and print a more informative error message.

from sbt-sonatype.

ok. I'll work on handling XML parsing exceptions

from sbt-sonatype.

thank you! at the moment, all of our travis-ci.org builds are affected.
unfortunately changing the plugin probably won't fix it, but being able to see the error response from sonatype would help tremendously. let me know if i can help in any way.

from sbt-sonatype.

I hate to be a "me too", but I'm now getting this constantly and cannot publish. :-(

from sbt-sonatype.

situation with sonatype seems to improve, some builds have gone through recently.
update: more scheduled maintenance :(
https://status.maven.org/

from sbt-sonatype.

Actually if sonatype API is down for such a long time (almost 2 days...), even if we add backoff retries, it will not solve this.

from sbt-sonatype.

That's true, but being able to see the error response from sonatype would help tremendously.

from sbt-sonatype.

I also introduced different timeout settings for creating a new stage (up to 5 min as this needs to be a single HTTP request) and for closing and promoting stages (up to 60 min). I hope this will mitigate this type of slow response issues.

from sbt-sonatype.

Brilliant 👍

from sbt-sonatype.

@mpollmeier Another improvement is that the latest version shows the error response in the warning log even if it is an HTML response :)

from sbt-sonatype.

yay thank you! 🙇‍♂️

from sbt-sonatype.