Maven Wagon

Use of proxy properties in lightweight http wagon is not thread-safe

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-beta-6
  • Fix Version/s: 2.0
  • Component/s: wagon-http-lightweight
  • Labels:
    None
  • Number of attachments :
    0

Description

The usage of system properties to configure the proxy for the lightweight wagon makes it not thread safe. E.g. as discovered by the Maven IT for MNG-2305, this concurrency issue makes parallel artifact resolution via proxy fail intermittently.

Moving on to Java 1.5+ APIs, it should be feasible to fix this via per-connection proxy settings.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. WAGON-346 LightWeight http wagon not thread-safe

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jan Sievers added a comment -

The only workaround we found is to use the commons http wagon implementation

<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-http</artifactId>
<version>1.0-beta-7</version>
</extension>
</extensions>
</build>

We also tried reducing the number of threads used to 1 uisng "-Daether.connector.wagon.threads=1" but this did not help.

This problem appears globally for us and changing all poms/parent poms to use a different wagon is not feasible.
Do you have other options for workarounds?

Thanks
Jan

Show
Jan Sievers added a comment - The only workaround we found is to use the commons http wagon implementation <build> <extensions> <extension> <groupId>org.apache.maven.wagon</groupId> <artifactId>wagon-http</artifactId> <version>1.0-beta-7</version> </extension> </extensions> </build> We also tried reducing the number of threads used to 1 uisng "-Daether.connector.wagon.threads=1" but this did not help. This problem appears globally for us and changing all poms/parent poms to use a different wagon is not feasible. Do you have other options for workarounds? Thanks Jan
Benjamin Bentmann made changes -
Field Original Value New Value
Link This issue relates to WAGON-346 [ WAGON-346 ]
Olivier Lamy made changes -
Status Open [ 1 ] Closed [ 6 ]
Assignee Olivier Lamy [ olamy ]
Fix Version/s 2.0 [ 17379 ]
Resolution Fixed [ 1 ]

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Benjamin Bentmann
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: