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/08 12:26:59 UTC
[jira] Created: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
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
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
[jira] Closed: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay closed MRM-769.
-----------------------------------
Resolution: Fixed
Work done in MRM-781has superseded this issue.
> 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
> Affects Versions: 1.0, 1.0.1, 1.0.2
> Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD
> Reporter: Andrew Heald
> Assignee: James William Dumay
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130139#action_130139 ]
Andrew Heald commented on MRM-769:
----------------------------------
We do. From our ultimate parent POM:
<distributionManagement>
<repository>
<id>catlin</id>
<name>Catlin Generated Releases</name>
<url>dav:http://maven.catlin.com:33030/archiva/repository/catlin</url>
</repository>
<snapshotRepository>
<id>catlin</id>
<name>Catlin Generated Snapshots</name>
<url>dav:http://maven.catlin.com:33030/archiva/repository/catlin</url>
<uniqueVersion>false</uniqueVersion>
</snapshotRepository>
</distributionManagement>
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130136#action_130136 ]
Andrew Heald commented on MRM-769:
----------------------------------
Not that I can see. Some more info, and let me know if there's more debug I can switch on.
Here's what the Maven build puts out:
08-Apr-2008 10:53:54 [INFO] [deploy:deploy]
08-Apr-2008 10:53:54 altDeploymentRepository = null
08-Apr-2008 10:53:54 [INFO] Retrieving previous build number from catlin
08-Apr-2008 10:53:54 Uploading: http://maven.catlin.com:33030/​archiva/​repository/​catlin/​com/​catlin/ ​InsuranceLedgerCore/​8.04-SNAPSHOT/​ InsuranceLedgerCore-8.04-SNAPSHOT.jar
08-Apr-2008 10:53:54 [INFO] Retrieving previous metadata from catlin
08-Apr-2008 10:53:55 [INFO] Uploading repository metadata for: 'artifact com.catlin:InsuranceLedgerCore'
08-Apr-2008 10:53:55 [INFO] Retrieving previous metadata from catlin
08-Apr-2008 10:53:55 [INFO] Uploading project information for InsuranceLedgerCore 8.04-SNAPSHOT
08-Apr-2008 10:53:55 [INFO] ------------------------------------------------------------------------
08-Apr-2008 10:53:55 [ERROR] BUILD ERROR
08-Apr-2008 10:53:55 [INFO] ------------------------------------------------------------------------
08-Apr-2008 10:53:55 [INFO] Error installing artifact's metadata: Error while deploying metadata: Failed to transfer file: http://maven.catlin.com:33030/​archiva/​repository/​catlin/​com/​catlin/ ​InsuranceLedgerCore/​8.04-SNAPSHOT/​ InsuranceLedgerCore-8.04-SNAPSHOT.pom. Return code is: 507 Insufficient Storage
And in archiva.log I see:
2008-04-08 10:53:53,844 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/8.04-SNAPSHOT/maven-metadata.xml" "Modify File (proxied)"
2008-04-08 10:53:54,141 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/8.04-SNAPSHOT/InsuranceLedgerCore-8.04-SNAPSHOT.jar" "Modify File"
2008-04-08 10:53:54,406 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/8.04-SNAPSHOT/InsuranceLedgerCore-8.04-SNAPSHOT.jar.md5" "Modify File"
2008-04-08 10:53:54,656 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/8.04-SNAPSHOT/InsuranceLedgerCore-8.04-SNAPSHOT.jar.sha1" "Modify File"
2008-04-08 10:53:54,672 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File (proxied)"
2008-04-08 10:53:54,906 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File"
2008-04-08 10:53:55,125 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml.md5" "Modify File"
2008-04-08 10:53:55,344 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml.sha1" "Modify File"
2008-04-08 10:53:55,625 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/8.04-SNAPSHOT/InsuranceLedgerCore-8.04-SNAPSHOT.pom" "Modify File"
The audit.log file adds nothing else to the above.
On a probably unrelated note, I do see errors from the previous day that look like this:
2008-04-07 18:00:03,845 [pool-1-thread-1] ERROR org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project - Unable to process model F:\var\data\archiva\data\repositories\catlin\com\catlin\CatFlap\CatFlapGatewayCore\2.4-SNAPSHOT\CatFlapGatewayCore-2.4-SNAPSHOT.pom due to : javax.jdo.JDODataStoreException : Insert request failed: INSERT INTO SA.ARCHIVA_PROJECT (RELOCATION_ARCHIVA_VERSIONED_REFERENCE_ID_OID,URL,DESCRIPTION,"NAME",ORIGIN,CI_MANAGEMENT_URL_OID,ISSUE_MANAGEMENT_URL_OID,WHEN_INDEXED,ORGANIZATION_NAME_OID,SCM_ARCHIVA_SCM_ID_OID,PARENT_PROJECT_ARCHIVA_VERSIONED_REFERENCE_ID_OID,PACKAGING,ARTIFACT_ID,GROUP_ID,VERSION) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
javax.jdo.JDODataStoreException: Insert request failed: INSERT INTO SA.ARCHIVA_PROJECT (RELOCATION_ARCHIVA_VERSIONED_REFERENCE_ID_OID,URL,DESCRIPTION,"NAME",ORIGIN,CI_MANAGEMENT_URL_OID,ISSUE_MANAGEMENT_URL_OID,WHEN_INDEXED,ORGANIZATION_NAME_OID,SCM_ARCHIVA_SCM_ID_OID,PARENT_PROJECT_ARCHIVA_VERSIONED_REFERENCE_ID_OID,PACKAGING,ARTIFACT_ID,GROUP_ID,VERSION) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:455)
at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519)
at org.jpox.store.StoreManager.insert(StoreManager.java:938)
at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667)
at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646)
at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1206)
at org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1277)
at org.apache.maven.archiva.database.jdo.JdoAccess.saveObject(JdoAccess.java:192)
at org.apache.maven.archiva.database.jdo.JdoAccess.saveObject(JdoAccess.java:165)
at org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.saveProjectModel(JdoProjectModelDAO.java:86)
at org.apache.maven.archiva.consumers.database.ProjectModelToDatabaseConsumer.processArchivaArtifact(ProjectModelToDatabaseConsumer.java:170)
at org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:52)
at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateUnprocessed(JdoDatabaseUpdater.java:154)
at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllUnprocessed(JdoDatabaseUpdater.java:88)
at org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:68)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
NestedThrowablesStackTrace:
ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'ARCHIVA_PROJECT_PK' defined on 'ARCHIVA_PROJECT'.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexChanger.insertAndCheckDups(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexChanger.doInsert(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexChanger.insert(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexSetChanger.insert(Unknown Source)
at org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(Unknown Source)
at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(Unknown Source)
at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
at org.jpox.store.rdbms.RDBMSManager.executeStatementUpdate(RDBMSManager.java:575)
at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:328)
at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519)
at org.jpox.store.StoreManager.insert(StoreManager.java:938)
at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667)
at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646)
at org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1206)
at org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1277)
at org.apache.maven.archiva.database.jdo.JdoAccess.saveObject(JdoAccess.java:192)
at org.apache.maven.archiva.database.jdo.JdoAccess.saveObject(JdoAccess.java:165)
at org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.saveProjectModel(JdoProjectModelDAO.java:86)
at org.apache.maven.archiva.consumers.database.ProjectModelToDatabaseConsumer.processArchivaArtifact(ProjectModelToDatabaseConsumer.java:170)
at org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:52)
at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateUnprocessed(JdoDatabaseUpdater.java:154)
at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllUnprocessed(JdoDatabaseUpdater.java:88)
at org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:68)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130138#action_130138 ]
Brett Porter commented on MRM-769:
----------------------------------
can you try dav:http:// for the upload instead of just http:// ?
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135516#action_135516 ]
Arnaud Heritier commented on MRM-769:
-------------------------------------
I have the same problem . I hope that MRM-781 can help to solve it.
I don't see how to reproduce it in a test environment.
I have it more and more often but it is certainly related to the number of build in our continuous integration server which is growing every day.
There is no error in logs.
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131564#action_131564 ]
Andrew Heald commented on MRM-769:
----------------------------------
Sadly, I can't mess with the builds involved in this problem without disrupting my team.
If I'm able to I'll reproduce this on a branch and in a VM, but this might take quite some time if it happens at all. I'll do my best.
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130137#action_130137 ]
Andrew Heald commented on MRM-769:
----------------------------------
I'm curious about the two log lines:
2008-04-08 10:53:54,672 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File (proxied)"
2008-04-08 10:53:54,906 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File"
Why the "proxied" bit. This file is in our Archiva repo and should not involve our proxy.
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130130#action_130130 ]
Brett Porter commented on MRM-769:
----------------------------------
are there any errors in the server logs?
> 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
>
> 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
[jira] Issue Comment Edited: (MRM-769) CLONE - 507 Insufficient
Storage when deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130137#action_130137 ]
drewpuppy edited comment on MRM-769 at 4/8/08 9:52 AM:
----------------------------------------------------------
I'm curious about the two log lines:
2008-04-08 10:53:54,672 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File (proxied)"
2008-04-08 10:53:54,906 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File"
Why the "proxied" bit? This file is in our Archiva repo and should not involve our proxy.
was (Author: drewpuppy):
I'm curious about the two log lines:
2008-04-08 10:53:54,672 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File (proxied)"
2008-04-08 10:53:54,906 [SocketListener0-49] INFO org.apache.archiva.AuditLog - catlin build_dev 10.1.0.121 "/com/catlin/InsuranceLedgerCore/maven-metadata.xml" "Modify File"
Why the "proxied" bit. This file is in our Archiva repo and should not involve our proxy.
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135527#action_135527 ]
Arnaud Heritier commented on MRM-769:
-------------------------------------
I made the change for new projects and those ones which wanted to update their settings.
They are now deploying with http:// .... .
I try to check tomorrow if this error occurs only for projects having always dav:http://
> 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
[jira] Updated: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-769:
-----------------------------
Fix Version/s: 1.1
> 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
[jira] Issue Comment Edited: (MRM-769) CLONE - 507 Insufficient
Storage when deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130110#action_130110 ]
drewpuppy edited comment on MRM-769 at 4/8/08 6:16 AM:
----------------------------------------------------------
I've cloned the original issue to reopen it, at Brett's suggestion. I don't have edit rights, so note that ....
The environment here is:
Server: Archiva 1.0.2 release candidate, standalone installation.
Client: Maven 2.0.8, JRockit R27.3.1 jdk1.5.0_11, Windows Server 2003 R2
This webdav behaviour occurs on differing artifact uploads, be they JARs, POMs or whatever. It is not a metadata thing.
was (Author: drewpuppy):
I've cloned the original issue to reopen it, at Brett's suggestion. I don't have edit rights, so note that ....
The environment here is:
Server: Archiva 1.0.2 release candidate.
Client: Maven 2.0.8, JRockit R27.3.1 jdk1.5.0_11, Windows Server 2003 R2
This webdav behaviour occurs on differing artifact uploads, be they JARs, POMs or whatever. It is not a metadata thing.
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130110#action_130110 ]
Andrew Heald commented on MRM-769:
----------------------------------
I've cloned the original issue to reopen it, at Brett's suggestion. I don't have edit rights, so note that ....
The environment here is:
Server: Archiva 1.0.2 release candidate.
Client: Maven 2.0.8, JRockit R27.3.1 jdk1.5.0_11, Windows Server 2003 R2
This webdav behaviour occurs on differing artifact uploads, be they JARs, POMs or whatever. It is not a metadata thing.
> 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
>
> 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
[jira] Assigned: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay reassigned MRM-769:
---------------------------------------
Assignee: James William Dumay (was: Joakim Erdfelt)
> 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: James William Dumay
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131363#action_131363 ]
Brett Porter commented on MRM-769:
----------------------------------
are you able to try Archiva trunk today to see if it resolves your issue?
> 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
>
> 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
[jira] Issue Comment Edited: (MRM-769) CLONE - 507 Insufficient
Storage when deploying artifact with webdav
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131363#action_131363 ]
brettporter edited comment on MRM-769 at 4/18/08 10:18 PM:
------------------------------------------------------------
are you able to try Archiva trunk (any revision after today) to see if it resolves your issue?
was (Author: brettporter):
are you able to try Archiva trunk today to see if it resolves your issue?
> 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
>
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135525#action_135525 ]
Brett Porter commented on MRM-769:
----------------------------------
Arnaud - I am quite hopeful it will, but we'll need someone to test the new version and confirm.
Also, you might try the reverse of my suggestion - using http:// instead of dav:http:// ? Or perhaps that is already happening too and it applies to both scenarios.
> 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
[jira] Updated: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MRM-769:
------------------------------------
Affects Version/s: 1.0
1.0.1
1.0.2
> 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
> Affects Versions: 1.0, 1.0.1, 1.0.2
> Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK 1.5.0_08, archiva HEAD
> Reporter: Andrew Heald
> Assignee: James William Dumay
> 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
[jira] Commented: (MRM-769) CLONE - 507 Insufficient Storage when
deploying artifact with webdav
Posted by "Andrew Heald (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131245#action_131245 ]
Andrew Heald commented on MRM-769:
----------------------------------
I've had to implement a workaround that effectively ends up using Archiva only as a proxy.
The original Archiva repo is now accessed through Apache's mod_dav. I've deleted my original Archiva repo and recreated it in the same name, but with a different repo directory, and configured it to proxy the now mod_dav managed repo.
All builds fine so far.
I note that there's discussion about replacing the WebDAV module in Archiva and I thoroughly endorse this. :-)
> 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
>
> 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