Subject | Connection Pooling and Concurrent Transactions |
---|---|
Author | dekhands lukeman |
Post date | 2011-02-12T15:22:58Z |
Hello,
I have a question.
We have an application that was originally designed for single users, using a
single Firebird jdbc connection. Now, we have a requirement that we allow
multiple simultaneous users which of course, will concurrently process
potentially long running transactions.
If replace our singleton connection with dedicated connections via connection
pooling, would this prevent or otherwise mitigate open result set cursor
contentions and other concurrency issues since the transaction would occur on
its own connection?
Thanks for your time.
Dave Krepow
[Non-text portions of this message have been removed]
I have a question.
We have an application that was originally designed for single users, using a
single Firebird jdbc connection. Now, we have a requirement that we allow
multiple simultaneous users which of course, will concurrently process
potentially long running transactions.
If replace our singleton connection with dedicated connections via connection
pooling, would this prevent or otherwise mitigate open result set cursor
contentions and other concurrency issues since the transaction would occur on
its own connection?
Thanks for your time.
Dave Krepow
[Non-text portions of this message have been removed]