We are having a weird sequencing problem with TopLink 10.1.3.5
We have a parent with a 1-many child.
When we do an insert of a parent and multiple child records we get the same sequence number assigned to a child record randomly and then error out with duplicate key error.
What could be the reason? We have the same sequencing information in the sessions.xml and the mappings. We use the default pre-allocation of 50 and we even tested it by increasing it to 500.
Has anyone seen this sort of a problem?
Thanks for the help
How have you configured Sequencing for the application, could it be that reads for the sequence number are occurring within your transaction? Try turning on TopLink logging to Fine or Finest and post what happens for the problem sequence.