Hi Serge, the default sequence manager implementation (a High/Low impl) cache sequence values. You could change this - version <=0.9.8: in OJB.properties (section SequenceManager), use another sequence manager implementation. Under [OJB]\src\java\org\apache\ojb\broker\util\sequence you could find all shipped sequence manger implementations
- version >=0.9.9.x (CVS): refactored sequence package, add sequence-manager element within the jdbc-connection-descriptor in repository file and declare the sequence-manager implementation class you want to use. Under [OJB]\src\java\org\apache\ojb\broker\util\sequence you could find all shipped sequence manger implementations Or try to use 'grabSize=1', or write your own sequence manager implementation, see shipped docs section 'sequence manager' regards, Armin ----- Original Message ----- From: "Boulay, Serge" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 30, 2003 5:46 PM Subject: Multiple VMS with ojb and sequences Hello All, We have a couple of developers testing ojb on different app servers . Each app server is hitting the same database (schema) . Does ojb check the seq table each time it inserts rows or does it cache sequence values ? We seem to be running into duplicate sequence values in the database . Whenever I insert a row with a pk that already exist with odmg it does not insert the row (only when I check the db do I discover that it is not there). In production everthing will be running off one app server , so was I just wondering if deploying the app on serveral machines and running them against the same database would cause this problem. Serge --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
