Hello!
Now, I've implemented the first solution proposed in the book you
suggested (Sequence bean generating and caching integer primary keys).
It works well, but at the very first usage of it the transaction times
out. Precisely, the call of
"SequenceEntityBean.getValueAfterIncrementingBy" seem
Try to take a look at the excellent EJB Design Patterns book by Floyd
Marinescu at TheServerSide.com:
http://www.theserverside.com/books/EJBDesignPatterns/index.jsp
There's a whole chapter [chapter 5] about primary key generation strategies,
maybe it might help you.
HTH
Martin
> -Original Me
Thanks!
On Tue, 23 Jul 2002 09:35:51 +0530 (IST), you wrote:
>Dimitri,
>As someone already pointed out, your pk generation strategy might not
>gaurentee absolutely unique integers under concurrent access situations.
>This problem has been debated extensively on different forums/lists and
>you ca
Dimitri,
As someone already pointed out, your pk generation strategy might not
gaurentee absolutely unique integers under concurrent access situations.
This problem has been debated extensively on different forums/lists and
you can find the concise results of those discussions by taking a look at
The method you have chosen doesn't give unique pk values with more than one
thread/user.
There are many many ways to do this right, including I think an id
generator bean included with jboss. Look in the archives.
david jencks
On 2002.07.22 13:25:58 -0400 Dimitri PISSARENKO wrote:
> Hello!
>
