RE: [bdbxml] Locker entries exceeded?
"Antony Grinyer" <antony.grinyer-TjPRh57ScDpaa/[email protected]> Mon, 26 Sep 2005 11:27:54 +0100
| Newsgroups | gmane.comp.db.dbxml.general |
|---|---|
| Message-ID | <989E1989F3130042879B902D175842163EFE81@msxmigration.cswgroup.local> |
Hi John, We changed the code to increase the max lockers number etc. and then stopped all the applications to ensure the environment was closed and removed; therefore, do you mean we need to delete all the __db, log, and containers files first to ensure the environment is recreated with the new locker settings? Thanks, Ant > -----Original Message----- > From: John Snelson [mailto:[email protected]]=20 > Sent: 26 September 2005 11:05 am > To: Antony Grinyer > Cc: [email protected] > Subject: Re: [bdbxml] Locker entries exceeded? >=20 > You will have to remove the old environement, and recreate it=20 > with the new configuration before the changes wil come into effect. >=20 > http://www.sleepycat.com/xmldocs/java/com/sleepycat/db/Environ > ment.html#remove(java.io.File,%20boolean,%20com.sleepycat.db.E nvironmentConfig) >=20 > John >=20 > Antony Grinyer wrote: > > Hi, > >=20 > > We're getting an error when running queries against a container=20 > > holding thousands of small XML documents: > >=20 > > *Lock table is out of available locker entries > > com.sleepycat.dbxml.XmlException: Error: Dbc::get: Not=20 > enough space,=20 > > errcode =3D DATABASE_ERROR* > >=20 > > We've increased the 3 parameters on the DB XML Environment=20 > objects to > > 10,000: > >=20 > > envConfig.setMaxLocks(10000); > > envConfig.setMaxLockers(10000); > > envConfig.setMaxLockObjects(10000); > >=20 > > ...but we still get the error after a few queries, can anyone shed=20 > > some light please? > >=20 > > Thanks, > > Ant > >=20 >=20 >=20 > -- > John Snelson, Berkeley DB XML Engineer > Sleepycat Software, Inc > http://www.sleepycat.com >=20 > Contracted to Sleepycat through Parthenon Computing Ltd=20 > http://blog.parthcomp.com/dbxml >=20 >=20 >=20 ------------------------------------------ To remove yourself from this list, send an email to [email protected]