I've experienced a weird problem in my servlet environment (caucho resin 1.2.6, RH8, sql server 2k, 0.9.7 using PB API) with the sequence manager. Until recently my application has run on 1 application server, with a grab size of 10 for sequences (I'm using the HI_LO seq manager) which was working fine. Now I added a second application server, behind a load balancer with the same settings (Sticky source IP). If I had a problem with sequences I would expect to see UNIQUE KEY constraint errors in my logs. Instead if 2 instances/servers of OJB grab the same or overlapping pools of keys, the first insert succeeds. The weird part is the second app server then inserts with the same already used primary key, and it appears to over-write the record that was already there, thus eating data and masking the problem by succeeding. Is this behavior intentional? Should I be running OJB in CS mode? I've tried to decrease the grab size to 1, hoping that will alleviate the problem until I find out more. I've also heard the CS mode has been broken for a while, so should I even mess with it?
I'm trying to hold on to .97 as long as I can to get something closer to v1.0, as .98 I had to roll back because of some other odd problems. Thanks for any input, Ryan
