From: Pierrick B. <pie...@cu...> - 2005-12-05 10:38:44
|
Hi, Ron Van den Branden wrote: > Thanks but no, this doesn't help. Changing recovery enabled to "no"=20 > indeed prevents journal logging, but the database stays inaccessible=20 > when read-only. Starting eXist with the startup script immediately exit= s=20 > with following error: >=20 > cluster.journal.maxStore 65000 > cluster.journal.shift 100 > configuration error: null > java.nio.channels.NonWritableChannelException > at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:818) > ... The next lines (thouse within eXist's control) would have been=20 interesting... > 2005-12-05 10:30:24,453 [main] DEBUG (TransactionManager.java=20 > [<init>]:74) - GroupCommits =3D false > 2005-12-05 10:30:24,563 [main] DEBUG (DBBroker.java [<init>]:182) -=20 > Loading symbol table from=20 > C:\eXist\eXist-1.0_ss20051203\webapp\WEB-INF\data\symbols.dbx > 2005-12-05 10:30:24,613 [main] DEBUG (DBBroker.java [<init>]:197) -=20 > fragmentation =3D 20 > 2005-12-05 10:30:24,643 [main] DEBUG (NativeBroker.java [<init>]:200) -= =20 > Initializing broker 25378506 Looks OK. It may be nice to add some more logging there. > So my question remains: is it possible to run eXist read-only? eXist is designed as such. Any other behaviour should be regarded as a bu= g. I'm afraid that we also lack test cases in this area... Cheers, --=20 Pierrick Brihaye, informaticien Service r=E9gional de l'Inventaire / DRAC Bretagne mailto:pie...@cu... / t=E9l : +33 (0)2 99 29 67 78 http://usenet-fr.news.eu.org/fr-chartes/rfc1855.html#31. L'avez-vous lu ? |