[
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
