You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "James William Dumay (JIRA)" <ji...@codehaus.org> on 2008/06/21 06:27:27 UTC

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

    [ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139195#action_139195 ] 

James William Dumay commented on MRM-769:
-----------------------------------------

Arnaud,
Are you able to build trunk and test that this is still an issue for you?

Thanks
James

> CLONE - 507 Insufficient Storage when deploying artifact with webdav
> --------------------------------------------------------------------
>
>                 Key: MRM-769
>                 URL: http://jira.codehaus.org/browse/MRM-769
>             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: Andrew Heald
>            Assignee: Joakim Erdfelt
>             Fix For: 1.1
>
>
> 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