Rick Hillegas-3 wrote
> Hi Abhi,
>
> Here is one more idea. I believe that you said that you are running an
> in-memory database. That means that you do not need to worry about
> leaking pre-allocated sequence numbers when your application exits. You
> can try setting the pre-allocation range to the maximum number with the
> following system property:
>
> -Dderby.language.sequence.preallocator=2147483647
>
> When I try that setting, my repro program runs without any lock
> contention.
>
> Hope this helps,
> -Rick
Hi
I am running derby embedded 10.13.1.1 with preallocator=2147483647, but stil
got 40XL1 error on concurrent inserts. Could you tell me, if there is some
reason to this? In my application, I am not selecting SYSSEQUENCES table.
Only I am doing is connection.prepareStatement("VALUES (NEXT VALUE FOR
SIP_Id_Generator_seq)").executeQuery().
--
Sent from:
http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
