Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0, 1.0.1, 1.0.2
-
None
-
mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD
Description
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.
Attachments
Issue Links
- depends upon
-
MRM-463 Metadata merging doesn't work.
- Closed
- is duplicated by
-
MRM-464 Metadata.xml files are not released from a filesystem lock in Win32
- Closed
- is related to
-
MRM-408 The mvn deploy:deploy-file command gives "Parent doesn't exist" in a fresh install
- Closed
- is superceded by
-
MRM-781 Removal of Archiva-Webdav implementation in favor of Jackrabbit-webdav
- Closed
- relates to
-
MRM-333 Tomcat deployment of archiva results in unstable instance.
- Closed
- supercedes
-
MRM-243 507 Insufficient Storage when deploying artifact with webdav
- Closed