Michael Kutschke created WAGON-502:
--------------------------------------

             Summary: Succesfull PUT times out on Nexus
                 Key: WAGON-502
                 URL: https://issues.apache.org/jira/browse/WAGON-502
             Project: Maven Wagon
          Issue Type: Bug
          Components: wagon-http, wagon-http-lightweight
    Affects Versions: 3.0.0
         Environment: Windows 7, Nexus 3.6.0, maven 3.5.2
            Reporter: Michael Kutschke


I am uploading artifacts manually to a raw Nexus repository using 
maven-wagon-plugin. After succesfull upload of the first file, nothing happens 
until read timeout is hit.

 

As far as I can tell, this problem happens with both http providers.

 

I have tried disabling pooling, setting -Dhttp.protocol.expect-continue=false.

I have tried uploading the file with curl, this gives the following output (and 
returns!):

 
{quote} * timeout on name lookup is not supported
* Trying 10.215.60.229...
* Connected to 10.215.60.229 (10.215.60.229) port 9081 (#0)
* Server auth using Basic with user 'deployment'
> PUT /repository/xcit-test/v_5.1.0/web/js.js HTTP/1.1
> Host: 10.215.60.229:9081
> Authorization: Basic ZGVwbG95bWVudDp4Y2l0ZGVwbG95bWVudDEyMw==
> User-Agent: curl/7.50.1
> Accept: */*
> Content-Length: 414
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 201 Created
< Date: Fri, 23 Feb 2018 09:34:46 GMT
< Server: Nexus/3.6.0-02 (OSS)
< X-Frame-Options: SAMEORIGIN
< X-Content-Type-Options: nosniff
< Content-Length: 0
<
* Connection #0 to host 10.215.60.229 left intact{quote}
 

I looked at the code of maven-wagon-plugin but did not find anything 
suspicious, and seeing that both providers seem to be affected, I assume the 
problem lies with a shared component of both providers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to