Christian:

Its easy to submit a Jira yourself.

First, register as a user on Apache Jira. This is no big deal except that this Jira will not obfuscate your email address in any email you create. The address will be visible on a public site when you create an issue..

OK, its one more userid/password to remember and one more email address leak to deal with. Use a non-critical address.

Then you log into the Jira site. Creating the issuefor this problem is a simple form submission at that point.

You will get an email whenever the status on this issue changes.

   -- Dan


Christian Zanata wrote:

On Mon, 2006-08-28 at 12:48 +0200, KÖLL Claus wrote:
i have posted a few weeks ago the same problem we have tested a lot of configs but it doesnt work ..
maybe its really a bug so we should open a jira issue


Hi,
could anybody open the issue? for our project it seems to be a serious
problem, but we don't know how to workaround it.

I could create the new issue, but I'm not skilled in managing
jackrabbit-jira issues, instead if someone create it I could attach my
logs or my configuration.

Thanks in advance for the help

claus

chris

-----Ursprüngliche Nachricht-----
Von: Christian Zanata [mailto:[EMAIL PROTECTED] Gesendet: Montag, 28. August 2006 12:07
An: [email protected]
Betreff: problems with re-indexing the workspace

Hi to all,
we have this problem on a production server:

[ERROR] 20060825 17:06:40
(org.apache.jackrabbit.core.observation.ObservationManagerFactory) -
Synchronous EventConsumer threw exception. java.lang.OutOfMemoryError

This error seems happening when the repository tries to re-index the
workspace, but we don't have more stack traces.

Our configuration is: tomcat 5.0 [256 up to 512 mb of ram] + jackrabbit
1.0.1 on jdk 1.4.2_12 on an Ibntel Xeon 3.2GHz with 2Gb of memory

an this are our libraries:
activation-1.1.jar
dom4j.jar
pdfbox-0.7.2.jar
antlr.jar
hibernate2.jar
catalina.jar
poi-3.0-alpha2-20060616.jar
poi-contrib-3.0-alpha2-20060616.jar
poi-scratchpad-3.0-alpha2-20060616.jar
cglib-full-2.0.2.jar
commons-beanutils-1.6.jar
commons-collections-3.1.jar
commons-digester-1.5.jar
commons-fileupload-1.0.jar
commons-logging-1.0.4.jar
commons-validator-1.1.3.jar
jackrabbit-core-1.0.1.jar
jackrabbit-index-filters-1.0.1.jar
jackrabbit-jcr-commons-1.0.1.jar
jakarta-oro-2.0.8.jar
slf4j-log4j12.jar
javamail-1.4.jar
struts-1.2.4.jar
jcr-1.0.jar
struts-el.jar
jta.jar
tm-extractors-0.4.jar
log4j-1.2.11.jar
xercesImpl-2.6.2.jar
concurrent.jar
lucene-1.4.3.jar
xml-apis.jar
db-ojb-1.0.4.jar
nekohtml.jar

this is also our repository.xml configuration:

<SearchIndex
class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
       <param name="path" value="${wsp.home}/index"/>
       <param name="textFilterClasses"
value="org.apache.jackrabbit.core.query.lucene.TextPlainTextFilter,
org.apache.jackrabbit.core.query.MsExcelTextFilter,
org.apache.jackrabbit.core.query.MsPowerPointTextFilter, org.apache.jackrabbit.core.query.MsWordTextFilter,
org.apache.jackrabbit.core.query.PdfTextFilter,
org.apache.jackrabbit.core.query.HTMLTextFilter,
org.apache.jackrabbit.core.query.XMLTextFilter,
org.apache.jackrabbit.core.query.RTFTextFilter,
                org.apache.jackrabbit.core.query.OpenOfficeTextFilter"/>
       <param name="useCompoundFile" value="true"/>
       <param name="minMergeDocs" value="100"/>
       <param name="volatileIdleTime" value="3"/>
       <param name="maxMergeDocs" value="100000"/>
       <param name="mergeFactor" value="10"/>
       <param name="bufferSize" value="10"/>
       <param name="cacheSize" value="1000"/>
       <param name="forceConsistencyCheck" value="false"/>
       <param name="autoRepair" value="true"/>
                <param name="respectDocumentOrder" value="false"/>
       <param name="analyzer"
value="org.apache.lucene.analysis.standard.StandardAnalyzer"/>
</SearchIndex>

could anybody heps us to understand what's happening?

thanks
chris




Reply via email to