|
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Olivier Grisel
Date: 26/06/07 21:29
Comment:
As far as I remember I could not reproduce the leak with the lucene filesystem backend of compass. So I think we should either switch to that backend or the JDBC + Derby backend by default.
Here is the exerpt of the compass-cfg.xml I used:
<!-- Lucene's native filesystem backend by default -->
<connection>
<file path="/opt/jboss/server/default/data/nxcompass-lucene-index"/>
</connection>
<!-- Sample JDBC + HSQL backend configuration
<connection>
<jdbc managed="true"
dialectClass="org.apache.lucene.store.jdbc.dialect.HSQLDialect"
deleteMarkDeletedDelta="3600000">
<dataSourceProvider>
<jndi lookup="java:/nxsearch-compass" />
</dataSourceProvider>
</jdbc>
</connection>
-->
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets