2

in a message driven bean i persist entries to lookup-table with unique entries. Basicly i create a select statement with the criteria api and if i don't find an entry, i create one.

Currently this code is running into mysql errors because in certain cases this entry creation (em.persist(entry)) would violate the unique constrain on my database. another instance of my mdb created the lookup entry after i didn't find it and before i could create it.

How can i handle this synchronization problem, so there still is only one entry?

MaDa
  • 10,511
  • 9
  • 46
  • 84
Laures
  • 5,389
  • 11
  • 50
  • 76

1 Answers1

1

You need to use SELECT FOR UPDATE or ensure uniqueness differently (e.g. generating unique part of the entry inside Java).

Hibernate supports pessimistic locks which I believe is just another name for the same thing.

mindas
  • 26,463
  • 15
  • 97
  • 154