[jira] Commented: (MRM-682) Archiva runs out of heap memory
[ http://jira.codehaus.org/browse/MRM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122530 ] James William Dumay commented on MRM-682: - I have turned off all the consumers to see if this improves the situation but ill be watching closely. > Archiva runs out of heap memory > --- > > Key: MRM-682 > URL: http://jira.codehaus.org/browse/MRM-682 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0, 1.0.1, 1.1 >Reporter: James William Dumay >Assignee: James William Dumay >Priority: Critical > Attachments: m2proxy.20080204.tar.gz, > maven.atlassian.com-log-20080203-0125.tgz, > maven.atlassian.com-logs-20080203-0745.tgz > > > Archiva appears to run out of heap memory frequently and the service crashes. > 512mb should be more than enough. -- 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-682) Archiva runs out of heap memory
[ http://jira.codehaus.org/browse/MRM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reassigned MRM-682: Assignee: James William Dumay > Archiva runs out of heap memory > --- > > Key: MRM-682 > URL: http://jira.codehaus.org/browse/MRM-682 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0, 1.0.1, 1.1 >Reporter: James William Dumay >Assignee: James William Dumay >Priority: Critical > Attachments: m2proxy.20080204.tar.gz, > maven.atlassian.com-log-20080203-0125.tgz, > maven.atlassian.com-logs-20080203-0745.tgz > > > Archiva appears to run out of heap memory frequently and the service crashes. > 512mb should be more than enough. -- 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-682) Archiva runs out of heap memory
[ http://jira.codehaus.org/browse/MRM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122529 ] Brett Porter commented on MRM-682: -- I spent some time profiling Archiva back in 0.9 to ensure there were no instances of this, particularly during scanning. With the current architecture it should be easy to identify a leak. Regardless - does disabling certain things you don't need help? I'd be interested to see what happens if the consumers were turned off and just proxying/webdav was in place. > Archiva runs out of heap memory > --- > > Key: MRM-682 > URL: http://jira.codehaus.org/browse/MRM-682 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0, 1.0.1, 1.1 >Reporter: James William Dumay >Priority: Critical > Attachments: m2proxy.20080204.tar.gz, > maven.atlassian.com-log-20080203-0125.tgz, > maven.atlassian.com-logs-20080203-0745.tgz > > > Archiva appears to run out of heap memory frequently and the service crashes. > 512mb should be more than enough. -- 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-541) convenient way to take Archiva proxies "offline"
[ http://jira.codehaus.org/browse/MRM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122459 ] Carlton Brown commented on MRM-541: --- I agree with this one... I would envision it as each proxy connector having a 'disabled' checkbox in the gui, with its state being persistent. I would implement this both for repository proxies and network proxies as well. > convenient way to take Archiva proxies "offline" > > > Key: MRM-541 > URL: http://jira.codehaus.org/browse/MRM-541 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.1 > > > I'm on a bad connection and proxying is very slow, making every archiva > request a multiple of that slowness. I don't want to temporarily modify the > configuration to disable the connectors (or even to turn on failure caching > which would help a little) - but I would like to have an admin feature to > temporarily turn off the proxy functionality altogether, considering Archiva > "offline" (but still serving requests, not that kind of offline :). -- 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-366) [Admin / Repository Scanning] Need informational messages describing purpose of sections
[ http://jira.codehaus.org/browse/MRM-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-366: - Fix Version/s: (was: 1.1) 1.0.2 > [Admin / Repository Scanning] Need informational messages describing purpose > of sections > > > Key: MRM-366 > URL: http://jira.codehaus.org/browse/MRM-366 > Project: Archiva > Issue Type: Bug > Components: documentation >Affects Versions: 1.0-alpha-1 >Reporter: Joakim Erdfelt > Fix For: 1.0.2 > > > The repository scanning screen is a bit sparse, and could use some > descriptive text explaining the purpose of the various sections. -- 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-391) Browse repository should display a suitable message when empty
[ http://jira.codehaus.org/browse/MRM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-391: - Fix Version/s: (was: 1.1) 1.0.2 > Browse repository should display a suitable message when empty > -- > > Key: MRM-391 > URL: http://jira.codehaus.org/browse/MRM-391 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.0.2 > > > When the configured repositories are empty, the browse page simply lists > nothing. > A suitable message indicating that no repositories are configured, or are not > indexed, or whatever is necessary should be displayed instead. -- 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-367) [Admin / Repositories] the consumers need to identify and highlight Permanent / Mandatory consumers better.
[ http://jira.codehaus.org/browse/MRM-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-367: - Fix Version/s: (was: 1.1) 1.0.2 > [Admin / Repositories] the consumers need to identify and highlight Permanent > / Mandatory consumers better. > --- > > Key: MRM-367 > URL: http://jira.codehaus.org/browse/MRM-367 > Project: Archiva > Issue Type: Bug > Components: design >Affects Versions: 1.0-alpha-1 >Reporter: Joakim Erdfelt > Fix For: 1.0.2 > > > Some consumers are flagged (on the compile time side) as permanent (aka > mandatory) and cannot be disabled. > The UI screens need to show this concept to the users. -- 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-573) purge does not delete the directory of a snapshot that is entirely removed
[ http://jira.codehaus.org/browse/MRM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-573: - Fix Version/s: (was: 1.1) 1.0.2 > purge does not delete the directory of a snapshot that is entirely removed > -- > > Key: MRM-573 > URL: http://jira.codehaus.org/browse/MRM-573 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-3 >Reporter: Brett Porter >Assignee: Maria Odea Ching > Fix For: 1.0.2 > > > this would be for the "delete released snapshots" purge most likely - I had > 1.0-SNAPSHOT not removed - but only the metadata and it's checksums remained. -- 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-580) Web app does not give error message when one defines an illegal directory for a Managed Repository
[
http://jira.codehaus.org/browse/MRM-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-580:
-
Fix Version/s: (was: 1.1)
1.0.2
> Web app does not give error message when one defines an illegal directory for
> a Managed Repository
> --
>
> Key: MRM-580
> URL: http://jira.codehaus.org/browse/MRM-580
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-3
> Environment: Debian GNU/Linux, Apache Tomcat 6.0.14
>Reporter: Duncan Doyle
>Priority: Minor
> Fix For: 1.0.2
>
>
> When you create a new Managed Repository and define a Directory in which
> Archiva has no write permissions, the webapp doesn't give an error message.
> When you click 'Add Repository' it just does nothing and remains on the same
> 'Add Managed Repository' page. Because of the fact that Archiva did not
> display an error message ("Cannot create directory, no write access." or
> something like that) it took me quite some time to figure out that I had made
> a typo in the Directory name.
--
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-632) Repository Purge Consumer throws Invalid Path to Artifact
[
http://jira.codehaus.org/browse/MRM-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-632:
-
Fix Version/s: (was: 1.1)
1.0.2
> Repository Purge Consumer throws Invalid Path to Artifact
> -
>
> Key: MRM-632
> URL: http://jira.codehaus.org/browse/MRM-632
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
>Affects Versions: 1.0
> Environment: Tomcat 6.0.14
> Windows Server 2003
>Reporter: Luke Amdor
> Fix For: 1.0.2
>
>
> I have the repository purge consumer enabled and configured as {{Repository
> Purge By Days Older Than}} to 0 and {{Repository Purge By Retention Count}}
> set to 3.
> This is with a clean database.
> I have more than 3 versions of org.irene:irene:2.0-SNAPSHOT already uploaded
> into the repository.
> When the repository is scanned:
> {noformat}
> 290870 [pool-2-thread-1] ERROR
> org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
> Consumer [repository-purge] had an error when processing file
> [D:\archiva-web\data\repositories\snapshots\org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar]:
> Invalid path to Artifact: filename format is invalid,expected timestamp
> format in filename.
> org.apache.maven.archiva.consumers.ConsumerException: Invalid path to
> Artifact: filename format is invalid,expected timestamp format in filename.
> at
> org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeConsumer.processFile(RepositoryPurgeConsumer.java:189)
> at
> org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:57)
> at
> org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117)
> at
> org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
> at
> org.apache.maven.archiva.repository.scanner.RepositoryScannerInstance.directoryWalkStep(RepositoryScannerInstance.java:138)
> at
> org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:173)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:391)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:344)
> at
> org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:120)
> at
> org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:64)
> at
> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:106)
> 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.runWorker(ThreadPoolExecutor.java:987)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
> at java.lang.Thread.run(Thread.java:595)
> Caused by:
> org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeException:
> Invalid path to Artifact: filename format is invalid,expected timestamp
> format in filename.
> at
> org.apache.maven.archiva.consumers.core.repository.RetentionCountRepositoryPurge.process(RetentionCountRepositoryPurge.java:102)
> at
> org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeConsumer.processFile(RepositoryPurgeConsumer.java:185)
> ... 20 more
> 290885 [pool-2-thread-1] ERROR
> org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
> Consumer [metadata-updater] had an error when processing file
> [D:\archiva-web\data\repositories\snapshots\org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar]:
> Unable to convert to artifact reference:
> org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar
> org.apache.maven.archiva.consumers.ConsumerException: Unable to convert to
> artifact reference:
> org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar
> at
> org.apache.maven.archiva.c
[jira] Updated: (MRM-448) validation for reports form
[ http://jira.codehaus.org/browse/MRM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-448: - Fix Version/s: (was: 1.1) 1.0.2 > validation for reports form > --- > > Key: MRM-448 > URL: http://jira.codehaus.org/browse/MRM-448 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0.2 > > > validation is missing - see MRM-329 -- 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-159) should not respond with a 404 if proxying a file results in a remote error
[ http://jira.codehaus.org/browse/MRM-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-159: - Fix Version/s: (was: 1.1) 1.0.2 > should not respond with a 404 if proxying a file results in a remote error > -- > > Key: MRM-159 > URL: http://jira.codehaus.org/browse/MRM-159 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Reporter: Brett Porter >Priority: Critical > Fix For: 1.0.2 > > > if any repository returns success, return success > otherwise, if any repository returns in error, return a generic error (500), > saying to check the logs. -- 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-677) Upgrade archiva to redback 1.0
[ http://jira.codehaus.org/browse/MRM-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-677: - Fix Version/s: (was: 1.1) 1.0.2 > Upgrade archiva to redback 1.0 > -- > > Key: MRM-677 > URL: http://jira.codehaus.org/browse/MRM-677 > Project: Archiva > Issue Type: Task > Components: build >Affects Versions: 1.0, 1.0.1 >Reporter: Maria Odea Ching > Fix For: 1.0.2 > > -- 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-402) javadoc jar is listed as just jar in the download box
[ http://jira.codehaus.org/browse/MRM-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-402: - Fix Version/s: (was: 1.1) 1.0.2 > javadoc jar is listed as just jar in the download box > - > > Key: MRM-402 > URL: http://jira.codehaus.org/browse/MRM-402 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.0.2 > > Attachments: archiva-bad-downloads-box.jpg > > > go to an artifact that has an attached javadoc jar - you will notice that it > is described as "Jar", not "Javadoc" -- 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-627) Archiva doesn't download SNAPSHOTs for proxied repositories.
[ http://jira.codehaus.org/browse/MRM-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-627: - Fix Version/s: (was: 1.1) 1.0.2 > Archiva doesn't download SNAPSHOTs for proxied repositories. > > > Key: MRM-627 > URL: http://jira.codehaus.org/browse/MRM-627 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0 > Environment: Linux, JDK 1.5, >Reporter: gumnaam > Fix For: 1.0.2 > > > I have setup Archiva Managed Internal Repository as my whole and sole mirror > in my settings.xml. > The settings.xml does not contain any other repository information, just the > mirror entry . > The Archiva Manged Internal Repository is set to proxy 4/5 external > repositories, > One of which contains certain SNAPSHOTs that I have as dependencies. > The proxy connector for this repository has snapshot policy set to "always", > I also tried > "daily", "hourly". But the SNAPSHOT is never downloaded any my build fails. > The log file shows no special activity. > Also I am including the link to the thread on user-list > http://www.nabble.com/Proxying-SNAPSHOT-repositories-td14336170.html -- 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-552) Download link should be entitled "Plugin", not "Jar" for maven plugins
[ http://jira.codehaus.org/browse/MRM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-552: - Fix Version/s: (was: 1.1) 1.0.2 > Download link should be entitled "Plugin", not "Jar" for maven plugins > -- > > Key: MRM-552 > URL: http://jira.codehaus.org/browse/MRM-552 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0.2 > > -- 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-606) docs appear in wrong directory for Archiva 1.0 release
[ http://jira.codehaus.org/browse/MRM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-606. Resolution: Fixed Fix Version/s: (was: 1.1) 1.0.1 > docs appear in wrong directory for Archiva 1.0 release > -- > > Key: MRM-606 > URL: http://jira.codehaus.org/browse/MRM-606 > Project: Archiva > Issue Type: Bug > Components: build >Affects Versions: 1.0 >Reporter: Brett Porter > Fix For: 1.0.1 > > > while it is fine on trunk, the docs appear in an archiva-1.0-docs.zip > subdirectory of the released distribution - check whether we need to lock > down to a better assembly plugin version -- 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
