Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-12429

badly formatted maven 2 source pom files cannot be migrated into nexus 3 repositories

    Details

    • Type: Story
    • Status: Refine
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.14.2, 3.2.0
    • Fix Version/s: None
    • Component/s: Migration
    • Labels:
      None

      Description

      1. Create a Maven 2 SNAPSHOT pom.xml in Nexus Repository Manager 2.14.2.
      Have the file contain this content:

      <?xml version="1.0" encoding="UTF-8"?>
      <!--
       !
       ! Empty for dummy loading
       !-->
      

      2. Perform a migration of the snapshots repo to Nexus 3.
      3. The migration process will appear stuck by this file and repeatedly treat the file as not valid. The migration will never complete.

      Nexus 3 log messages look like this and repeat forever:

      2017-02-13 16:12:23,116+0100 WARN  [plan-executor-7-thread-3] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Leaving failure mode
      2017-02-13 16:12:23,989+0100 WARN  [change-processing-9-thread-1] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Request failed: no more data available START_DOCUMENT seen ...<!--\n !\n ! Empty for dummy loading\n !-->... @5:6
      2017-02-13 16:12:23,989+0100 INFO  [change-processing-9-thread-1] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Delaying until Mon Feb 13 16:12:28 CET 2017
      2017-02-13 16:12:23,992+0100 WARN  [change-processing-9-thread-2] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Leaving failure mode
      2017-02-13 16:12:25,005+0100 WARN  [change-processing-9-thread-1] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Request failed: no more data available START_DOCUMENT seen ...<!--\n !\n ! Empty for dummy loading\n !-->... @5:6
      2017-02-13 16:12:25,005+0100 INFO  [change-processing-9-thread-1] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Delaying until Mon Feb 13 16:12:30 CET 2017
      2017-02-13 16:12:25,292+0100 WARN  [change-processing-9-thread-2] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Leaving failure mode
      2017-02-13 16:12:26,020+0100 WARN  [change-processing-9-thread-1] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Request failed: no more data available START_DOCUMENT seen ...<!--\n !\n ! Empty for dummy loading\n !-->... @5:6
      2017-02-13 16:12:26,021+0100 INFO  [change-processing-9-thread-1] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Delaying until Mon Feb 13 16:12:31 CET 2017
      2017-02-13 16:12:26,505+0100 WARN  [change-processing-9-thread-2] admin com.sonatype.nexus.migration.client.http.MigrationRequestMonitorImpl - Leaving failure mode
      

      Nexus 2 shows the file being requested over and over:

      10.32.51.48 - - [13/Feb/2017:23:10:12 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 1
      10.32.51.48 - - [13/Feb/2017:23:10:17 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      10.32.51.48 - - [13/Feb/2017:23:10:22 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      10.32.51.48 - - [13/Feb/2017:23:10:27 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      10.32.51.48 - - [13/Feb/2017:23:10:32 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      10.32.51.48 - - [13/Feb/2017:23:10:38 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      10.32.51.48 - - [13/Feb/2017:23:10:43 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      10.32.51.48 - - [13/Feb/2017:23:10:48 +0100] "GET /nexus/service/siesta/migrationagent/repository-content/snapshots/org%2Fapache%2Fwoden%2Fwoden%2F1.0-SNAPSHOT%2Fwoden-1.0-20121120.081343-1.pom HTTP/1.1" 200 79 2
      

      Expected

      • migration should not appear hung in the UI for any file migration problem
      • Nexus 3 should ALWAYS LOG THE URL REQUESTED OF THE FILE WITH THE PROBLEM when a content Request failed - you should not need to examine nexus 2 logs to figure out the problem file path, which repository, which file
      • badly formatted files in a Maven 2 source repository (release or snapshot) are unavoidable - they should always be migrated
      • tasks which purge files on the nexus 3 side should be able to purge such migrated files, despite their content, otherwise there will be no way to clean these up in the future

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Michael Prescott Michael Prescott
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title