You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/10/08 02:49:33 UTC
[jira] Commented: (MRM-1420) Archiva browse urls are very slow
[ http://jira.codehaus.org/browse/MRM-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238072#action_238072 ]
Brett Porter commented on MRM-1420:
-----------------------------------
this appears to be when an abnormally long indexing queue is in place. The work on upgrading the indexer might help, and a workaround is to minimize the amount of scanning, and the content scanned.
I'll attaching a temporary JSP file that can be used to inspect the state of the queues on a running server to see if that's the case for anyone hitting this issue. I'll look into making it a more permanent feature under the administration section in the future.
> Archiva browse urls are very slow
> ---------------------------------
>
> Key: MRM-1420
> URL: http://jira.codehaus.org/browse/MRM-1420
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Affects Versions: 1.3.1
> Reporter: Wendy Smoak
>
> We are running Archiva behind a proxy and getting '502 Proxy Error' (Reason: Error reading from remote server) quite often on .../browse/... urls.
> Accessing Archiva directly on port 8080 results in the page eventually loading, but it takes more than five minutes (which causes the proxy to time out.)
> While browse is slow, .../repository/xxx/... urls continue to respond quickly (so Maven builds are not affected.)
--
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