You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Marc Lustig (JIRA)" <ji...@codehaus.org> on 2009/09/17 10:41:57 UTC
[jira] Created: (MRM-1253) Artifacts cannot be found using the
Search function
Artifacts cannot be found using the Search function
---------------------------------------------------
Key: MRM-1253
URL: http://jira.codehaus.org/browse/MRM-1253
Project: Archiva
Issue Type: Bug
Components: indexing, repository scanning, search
Affects Versions: 1.2.2, 1.2.1, 1.2
Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
Reporter: Marc Lustig
Priority: Blocker
Numerous artifacts cannot be found using the Search function.
The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
The artifacts can be found using the Browse function and using WebDAV.
The problem persists since Archiva 1.2.0.
The following effort has been untertaken to solve the problem:
1. deleting repo/.index and repo/.indexer
2. touching all files and dirs in repo recursively
3. running the repo scan
4. waiting some hours to finish the procedure
After this process, the artifacts still cannot be found. The index-database has the following sizes:
6.1M /opt/managed_repos/internal/.index
8.7M /opt/managed_repos/internal/.indexer
Example:
search for "xmlbeans"
result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
The Total File Count of the repo is 129542.
Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191929#action_191929 ]
Maria Odea Ching commented on MRM-1253:
---------------------------------------
Looking at the repository scanning and indexing debug logs from Marc, there were some logs for a couple of xmlbeans artifacts that says it was added to the indexing queue. I didn't see any logs regarding it being actually indexed whereas there were logs for that for other artifacts. The log snippet were not complete though so it is possible that the indexing task for the xmlbeans artifacts just wasn't executed yet. I'll see what I can dig up further.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193791#action_193791 ]
Maria Odea Ching commented on MRM-1253:
---------------------------------------
I found some artifacts in our internal Archiva repository that I wasn't able to search for. I re-indexed the repository and after a while, I was able to search for these artifacts. I found a few other artifacts on a larger repository which I wasn't able to find from the Archiva search. I'll try re-indexing this repository and see if I can search for them later.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Jevica Arianne B. Zurbano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jevica Arianne B. Zurbano closed MRM-1253.
------------------------------------------
Resolution: Fixed
Assignee: Jevica Arianne B. Zurbano
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Assignee: Jevica Arianne B. Zurbano
> Priority: Blocker
> Fix For: 1.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191305#action_191305 ]
Maria Odea Ching commented on MRM-1253:
---------------------------------------
Ahh.. you're using Tomcat, it's that logging problem again. I was running the standalone bundle so the above config was working fine.
I found this in Google which could possibly solve the logging problems:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-11968.html
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Jevica Arianne B. Zurbano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206599#action_206599 ]
Jevica Arianne B. Zurbano commented on MRM-1253:
------------------------------------------------
I have verified the issue using Archiva r898186 with a 12 GB repository.
Artifacts that did not appear in Archiva browse appeared after forcing a repository scan.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191465#action_191465 ]
Marc Lustig commented on MRM-1253:
----------------------------------
hmm, we have other Appenders configured that use pretty much the same ConversionPattern.
It's not urgent now as I have commented out the snippet, but I wonder what is really causing the NPE.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191301#action_191301 ]
Maria Odea Ching commented on MRM-1253:
---------------------------------------
Hi Marc, you need to add the following config in log4j.xml:
{code}
<appender name="repoScanLog" class="org.apache.log4j.DailyRollingFileAppender">
<param name="file" value="${appserver.base}/logs/archiva-repo-scanning.log" />
<param name="append" value="true" />
<param name="datePattern" value="'.'yyyy-MM-dd" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss} %m%n"/>
</layout>
</appender>
<logger name="org.apache.maven.archiva.consumers" additivity="false">
<level value="debug"/>
<appender-ref ref="repoScanLog"/>
</logger>
<logger name="org.apache.archiva.consumers" additivity="false">
<level value="debug"/>
<appender-ref ref="repoScanLog"/>
</logger>
<logger name="org.apache.maven.archiva.repository.scanner" additivity="false">
<level value="debug"/>
<appender-ref ref="repoScanLog"/>
</logger>
<logger name="org.apache.maven.archiva.scheduled.executors" additivity="false">
<level value="debug"/>
<appender-ref ref="repoScanLog"/>
</logger>
{code}
I'm having a hard time reproducing this problem. The repository I was using was not very large though, so that could also be a factor as well. Thanks in advance for your help in debugging this :)
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191393#action_191393 ]
Brett Porter commented on MRM-1253:
-----------------------------------
the timing is probably not the important thing, so you could just remove %d{...} from the pattern layout
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191351#action_191351 ]
Marc Lustig commented on MRM-1253:
----------------------------------
tomcat seems to use java.util.logging, so there is hardly any conflict between different versions of log4j or commons-logging.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194506#action_194506 ]
Maria Odea Ching commented on MRM-1253:
---------------------------------------
The indexing is taking a while to complete for large repositories. I had been scanning a 40gb repository and its been taking a few days for the indexing to completely finish. Can someone confirm if the artifact that cannot be searched appeared after a few days?
MRM-1260 can also be the cause why some artifacts do not appear in the search.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193682#action_193682 ]
Maria Odea Ching commented on MRM-1253:
---------------------------------------
Hi Marc,
I took a look at the last log file you've sent, I think it's still not complete :( The last artifact in the logs that was added to the index was way back above the xmlbeans artifact, so I don't think the xmlbeans were indexed yet in the logs. What are the other artifacts that doesn't show up in the search which I could check against the log file?
Thanks,
Deng
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191467#action_191467 ]
Wendy Smoak commented on MRM-1253:
----------------------------------
I have the same problem. Artifacts that I *know* are in the repository do not show up in a search, and no amount of scanning and updating helps.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194712#action_194712 ]
Brett Porter commented on MRM-1253:
-----------------------------------
note that the banner that indicates the scanning is complete no longer means that the artifacts have been indexed, since they are done in a parallel queue. The improvements I've just made to performance of the indexing may help here.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191303#action_191303 ]
Marc Lustig commented on MRM-1253:
----------------------------------
with this snippet I get endless
java.lang.NullPointerException
log4j:ERROR Error occured while converting date.
not sure what is wrong thou
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1253:
----------------------------------
Fix Version/s: (was: 1.2.3)
1.3
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191299#action_191299 ]
Marc Lustig commented on MRM-1253:
----------------------------------
I would like to help debugging this if you could help me to adjust log4j.xml in such way that repo-scan is debugged into a separate file.
Especially I need to know which package-names are relevant.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194510#action_194510 ]
Marc Lustig commented on MRM-1253:
----------------------------------
hi Deng, the scan-process had definately completed.
I took the logfile even a day after the scan took place.
This repo has just around 12 GB and it's a high performance server with SAN-volumes. It never took more than 2 hours here.
I will see if I can find other artifacts that do not show up in the search function. Recently there have been plenty of them.
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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-1253) Artifacts cannot be found using the
Search function
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1253:
----------------------------------
Fix Version/s: 1.2.3
> Artifacts cannot be found using the Search function
> ---------------------------------------------------
>
> Key: MRM-1253
> URL: http://jira.codehaus.org/browse/MRM-1253
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning, search
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Environment: RHEL 4, Tomcat 6.0.18, JDK 1.6.0_07
> Reporter: Marc Lustig
> Priority: Blocker
> Fix For: 1.2.3
>
>
> Numerous artifacts cannot be found using the Search function.
> The repository concerned has permissions for user guest as Repository Observer, meaning anonymous access is allowed.
> The artifacts can be found using the Browse function and using WebDAV.
> The problem persists since Archiva 1.2.0.
> The following effort has been untertaken to solve the problem:
> 1. deleting repo/.index and repo/.indexer
> 2. touching all files and dirs in repo recursively
> 3. running the repo scan
> 4. waiting some hours to finish the procedure
> After this process, the artifacts still cannot be found. The index-database has the following sizes:
> 6.1M /opt/managed_repos/internal/.index
> 8.7M /opt/managed_repos/internal/.indexer
> Example:
> search for "xmlbeans"
> result: 2 artifacts containing "xmlbeans" in the package name, but NOT the artifact whose artifactId is xmlbeans
> The Total File Count of the repo is 129542.
> Since the search-function is the most important function on the web-UI, we'd consider this a major blocker.
--
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