Delivery Manager Tool - Extraction Discovery - Error - Connection Exception 400 - Repository version policy RELEASE does not allow metadata in path maven-metadata xml


 When using the Delivery Manager Tool (DMT), an error is encountered during Extraction/Discovery step for Maven Repository and the Automatic Remediation goes in a loop:

  • Connection Exception: 400 - Repository version policy: RELEASE does not allow metadata in path: ../maven-metadata.xml" 

As shown in the below screenshot (this screenshot is from the logs generated during the DMT process - please see CAST Management Studio - Information - How to find logs for more information on how to find this log):

Observed in CAST AIP

8.3.x (tick)
Observed on RDBMS
Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

  1. Create a new version for an application
  2. Deliver code through DMT
  3. Error in the Extraction/Discovery step 
Impact of the Problem

The impact of the problem on the analysis or the dashboard is

  • Maven project will not be packaged - hence the pom and jar files will not be resolved. 
Action Plan
  1. Open the Extraction log and you will see the below error -

    cast.dmt.engine.extractor.jee.maven.http.versionMetadataRetrievalFailed Unkown format id: cast.dmt.engine.extractor.jee.maven.http.versionMetadataRetrievalFailed => %URL%="http://<maven URL>/content/repositories/" %MESSAGE%="Connection Exception: 400 - Repository version policy: RELEASE does not allow metadata in path: com/<Maven Repository Path>/maven-metadata.xml" Exception: 400 - Repository version policy: RELEASE does not allow metadata in path: com/<Maven Repository Path>/maven-metadata.xml

    As per the documentation for the JEE Maven HTTP Extractor 2.0, the error - "cast.dmt.engine.extractor.jee.maven.http.versionMetadataRetrievalFailed" - means that the extractor is not able to connect to the Maven URL or the metadata.xml file to resolve the pom and jars.

    Without the data required to identify the files for the SNAPSHOT, the artifact can't be extracted

  2. To confirm if there is an issue with the maven URL/the metadata.xml file, open the same using Internet Explorer. 
    • This error shows that the Maven URL you are trying to connect to does not have any content. It is a corruption in the maven repository. Until and unless it is fixed, the jars will not be extracted. 
  3. To solve the issue, you need to make sure that you retrieve the correct maven repository and run the packaging again. 
  4. If this does not solve your issue, contact CAST Technical Support with the Relevant Input

 Ticket # 20299
Related Pages