You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Andrew Heald (JIRA)" <ji...@codehaus.org> on 2008/04/07 11:25:59 UTC
[jira] Issue Comment Edited: (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&focusedCommentId=129985#action_129985 ]
drewpuppy edited comment on MRM-243 at 4/7/08 4:25 AM:
----------------------------------------------------------
This issue is not fixed in Archiva 1.0.1 and pops up at least once a day on our most complex integration build, though never for our other builds.
Client side environment here: Maven 2.0.8 and we're using wagon-webdav 1.0-beta-2. Windows.
I replaced plexus-urils 1.4 with 1.5.1 in Archiva but that hasn't fixed the problem.
Please reopen this issue, or shall I create a clone?
was (Author: drewpuppy):
This issue is not fixed in Archiva 1.0.1 and pops up at least once a day on our most complex integration build, though never for out other builds.
Client side environment here: Maven 2.0.8 and we're using wagon-webdav 1.0-beta-2.
I replaced plexus-urils 1.4 with 1.5.1 in Archiva but that hasn't fixed the problem.
Please reopen this issue, or shall I create a clone?
> 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
> Affects Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-beta-1, 1.0-beta-2
> Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD
> Reporter: Magne Rasmussen
> Assignee: Joakim Erdfelt
> 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