You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/09/21 21:34:12 UTC

[jira] Commented: (MRM-243) 507 Insufficient Storage when deploying artifact with webdav

    [ http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107974 ] 

Joakim Erdfelt commented on MRM-243:
------------------------------------

I was able to duplicate this problem on the following environment ...

Tested on WinXP(SP2) w/ Tomcat 5.0.28.
Using Archiva SVN Trunk r577463
JDK 1.5.0_11
Using the configuration specified at http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat#ArchivaonTomcat-Tomcat5.0.xSpecifics

I created a simple project with a 1.1 version and a copy of the project with a 1.2-SNAPSHOT version.

The first deploy (of version 1.1) to the internal repo succeeded, the next deploy (of version 1.2-SNAPSHOT) encountered the "507 Insufficient Storage" problem.

> 507 Insufficient Storage when deploying artifact with webdav
> ------------------------------------------------------------
>
>                 Key: MRM-243
>                 URL: http://jira.codehaus.org/browse/MRM-243
>             Project: Archiva
>          Issue Type: Bug
>          Components: web application
>         Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD
>            Reporter: Magne Rasmussen
>            Assignee: Brett Porter
>             Fix For: 1.0-beta-3
>
>
> Sometimes when deploying with dav I get a "507 Insufficient Storage" error.
> The artifact (.../group/artifact/version/artifact-version.jar) gets deployed (with checksums).
> The metadata (.../group/artifact/version/maven-metatdata.xml) gets deployed (with checksums).
> It seems to happen when maven tries to upload the updated parent metadata (.../group/artifact/maven-metadata.xml). The checksums for this metadata deploys OK.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira