Ok, so it is working.... for some reason when i was using an older version of ojb and hsqldb it was going up in jumps of the grabsize, so i just assumed that was what it did!
Anyway, the real problem i've had is that it has been going incremental up to a certain point in time, then it jumped about 50 places forward, then went incremental for a week or so and then jumped back and started overwriting existing objects, which obviously isnt good. I've decided to convert to letting mysql do the incrementing, and tell ojb to use native impl. Daniel. > -----Original Message----- > From: Pulat Yunusov [mailto:[EMAIL PROTECTED] > Sent: 18 October 2004 15:19 > To: OJB Users List > Subject: Re: HighLowSequenceManager chaos > > > Grab size refers to the number of consecutive values from which the > sequence manager issues primary keys until it reaches a value equal to > the max_key - 1. Then the max_key is increased by the grab size, and the > sequence manager continues to issue primary keys until it exhausts the > sequence again. > > Pulat > > Daniel Perry wrote: > > Hi, > > I've been trying to debug some problems in our software, and it > seems that > > the High Low Sequence Manager has gone a bit mad! > > > > I am seeing some wierd stuff going on - the sequence manager has NO > > settings, so should be acting in the default configuration. > The OJB_HL_SEQ > > is showing grabsizes of 20, and multiples of 20 in the max > column, but it > > doesnt seem to be using them. eg, i initialise the app and in > OJB_HL_SEQ i > > see: > > > > SEQ_pdp,deprecatedColumn,160,209 > > > > But when i insert data, i get id's of 161,162,163. I would expect > > 180,200,220. When i go to the HL_SEQ table after shutting down > the app, i > > see that the MAX_KEY is only 180. I've turned on debugging and i see > > messages like the following, which look right to me, except > that it comes up > > with the same message each time - it should be incremented right? > > > > > [org.apache.ojb.broker.util.sequence.SequenceManagerHighLowImpl] > DEBUG: new > > sequence was > > > [EMAIL PROTECTED] > ame=SEQ_pd > > > p,fieldName=deprecatedColumn,grabSize=20,version=9,maxKey=180,curr > entKey=160 > > ] > > > > Anyone seen this kind of problem before? > > > > Daniel. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
