Maven deploy to staging on oss.sonatype.org having issues

[Joakim Erdfelt]

See staging repo `jetty-1467` (and `jetty-1466`, now dropped) ...

Today a strange new behavior of oss.sonatype.org staging appeared.

The first file in the deploy fully uploads (such as the main jar artifact in a maven2 build) , but the server doesn't finish, leaving the maven-deploy-plugin waiting infinitely for progress to complete.

Other artifacts (such as the -source.jar, -javadoc.jar, md5's, sha's, etc..) are not even attempted, because the process is stuck waiting on oss.sonatype.org.

This behavior is occurs on Java Oracle 8u202 and OpenJDK 11.0.2 (haven't tested on other JVMs)

This behavior also happens with maven-deploy-plugin 2.6 or 3.0.0-M1 (haven't tested other versions)

The machine that handles our deploys has been stable and without software updates for about 6 months now, so it's not a software change on our end causing it.

Is there something going on at oss.sonatype.org? (past changes on oss.sonatype.org required us to update our JVM and/or our plugins to support the process)

Thanks,

- Joakim Erdfelt (Eclipse Jetty Dev)

[Peter Lynch]

On Tue, Apr 16, 2019 at 4:44 PM Joakim Erdfelt <joakim....@gmail.com> wrote:

See staging repo `jetty-1467` (and `jetty-1466`, now dropped) ...

Today a strange new behavior of oss.sonatype.org staging appeared.

The first file in the deploy fully uploads (such as the main jar artifact in a maven2 build) , but the server doesn't finish, leaving the maven-deploy-plugin waiting infinitely for progress to complete.

It might be helpful to see 

- the last lines of a Maven build debug output -X that hung, or even the regular output

- the thread dump of the maven process when hung

- knowing the exact URL in progress that is hung and how large the file that is hanging is

- I noticed maven 3.6.0 is being used - I assume that it has been used for the past 6 months without issue?

An issue can be filed at https://issues.sonatype.org/projects/OSSRH with this information if desired not to share here.

Other artifacts (such as the -source.jar, -javadoc.jar, md5's, sha's, etc..) are not even attempted, because the process is stuck waiting on oss.sonatype.org.

This behavior is occurs on Java Oracle 8u202 and OpenJDK 11.0.2 (haven't tested on other JVMs)

This behavior also happens with maven-deploy-plugin 2.6 or 3.0.0-M1 (haven't tested other versions)

The machine that handles our deploys has been stable and without software updates for about 6 months now, so it's not a software change on our end causing it.

Is there something going on at oss.sonatype.org? (past changes on oss.sonatype.org required us to update our JVM and/or our plugins to support the process)

Thanks,

- Joakim Erdfelt (Eclipse Jetty Dev)

--
You received this message because you are subscribed to the Google Groups "OSSRH Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ossrh-users...@glists.sonatype.com.
To post to this group, send email to ossrh...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/ossrh-users/CABH5f91QbR6iJx0fNV1_XnU%2BGPKH5%2Bm_m%2B3cTWW3H%2BzdLw52Ew%40mail.gmail.com.

--

Peter Lynch Senior Product Support Engineer

[Joakim Erdfelt]

Success!

I switched from http to https on ...

  <distributionManagement>

    <repository>

      <id>oss.sonatype.org</id>

      <name>Jetty Staging Repository</name>

      <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>

    </repository>

    <snapshotRepository>

      <id>oss.sonatype.org</id>

      <name>Jetty Snapshot Repository</name>

      <url>https://oss.sonatype.org/content/repositories/jetty-snapshots/</url>

    </snapshotRepository>

  </distributionManagement>

That <distributionManagement> has been unchanged since 2013.

- Joakim

[Peter Lynch]

On Tue, Apr 16, 2019 at 5:23 PM Joakim Erdfelt <joakim....@gmail.com> wrote:

Success!

I switched from http to https on ...

  <distributionManagement>

    <repository>

      <id>oss.sonatype.org</id>

      <name>Jetty Staging Repository</name>

      <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>

    </repository>

    <snapshotRepository>

      <id>oss.sonatype.org</id>

      <name>Jetty Snapshot Repository</name>

      <url>https://oss.sonatype.org/content/repositories/jetty-snapshots/</url>

    </snapshotRepository>

  </distributionManagement>

That <distributionManagement> has been unchanged since 2013.

Glad to hear you solved this.

I'm surprised by this statement though because since 2014 we encouraged all users to use https://oss.sonatype.org.