[
http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107975
]
Joakim Erdfelt commented on MRM-243:
------------------------------------
One extra note about previous comment.
The metadata upload that caused the "507 Insufficient Storage" error occured
when the SNAPSHOT deploy attempted to upload the metadata file. It did not
conflict with the maven-metadata.xml from the previous deploy (as that was on a
different repository). It appears that the previous request for the
maven-metadata.xml causes the problem with the deploy of the updated
maven-metadata.xml file.
More research is needed here.
I would hate to see this be a problem in the simple-webdav impl.
> 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
