[
http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95492
]
Joakim Erdfelt commented on MRM-243:
------------------------------------
This can occur (according to the code) due to the following ....
# temp directory not specified in system environment.
# temp directory is full.
# temp directory has too many files in it.
# java.io can't flush contents to disk.
# java.io can't write bytes to disk.
That's it.
A stacktrace from the server side should help narrow down which of these is
causing the 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
> Fix For: 1.0
>
>
> 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
