Nitish Sinha wrote:
Hi Derby User Team,
Do you have any updates on this issue? Since it been a long time we
submitted this problem.
Most of our clients are struck because of this problem because this is a
production issue..
Respond as soon as possible so that we can proceed further.Suggest us
how can we avoid this exception. So that we can implement this in our
application.
I am attaching all previous mails send to you regarding this issue.
Hello Nitish,
Without knowing more about the isolation level you use, the tables in
the database and the queries you are executing against Derby, it is hard
to give you an answer.
A few general observations/questions:
1) You say you are using Derby version 10.0. Is this correct? If so, is
it possible for you to upgrade to a newer version (say 10.2.2.0) and see
if you get the same problems?
2) Do you have many concurrent connections?
3) Are your transactions very long?
4) Do your queries touch many rows?
More information about the load is appreciated.
You could also try to play a little with some of these properties to
analyze your problem or see if they problems go away:
derby.locks.deadlockTimeout
derby.locks.deadlockTrace
derby.locks.escalationThreshold
derby.locks.monitor
derby.locks.waitTimeout
Consult the Tuning Guide for more information.
regards,
--
Kristian
Regards,
Nitish P. Sinha
L&T Infotech,Mumbai
Phone: +91-22-56948484 Ext-6310
Mobile :9820748213
______________________________________________________________________
------------------------------------------------------------------------
Hi Derby User Team,
Do you have any updates on this issue? Since it been a long time we submitted
this problem.
Most of our clients are struck because of this problem. Respond as soon as
possible so that we can proceed further.
Suggest us how can we avoid this exception. So that we can implement this in
our application.
Thanks in Advance.
Best Regards,
Sridhar
----- Forwarded by Sridharsingh Inder/LNTINFOTECH on 11/30/2006 11:22 AM -----
Sridharsingh Inder/LNTINFOTECH
11/14/2006 05:52 PM
To
[email protected]
cc
[EMAIL PROTECTED]
Subject
Query regarding derby
Hi Derby User Team,
Do you have any updates on this issue?
Best Regards,
Sridhar
----- Forwarded by Sridharsingh Inder/LNTINFOTECH on 11/14/2006 05:50 PM -----
Sridharsingh Inder/LNTINFOTECH
11/10/2006 11:17 AM
To
[email protected]
cc
[email protected], [EMAIL PROTECTED]
Subject
Re: Query regarding derby
Hi Derby User Team,
Thanks for your immediate response.
The derby version is mentioned below
Bundle-Name: Apache Derby 10.0
Bundle-Version: 10.0.2000001
DERBY_DRIVER = org.apache.derby.jdbc.EmbeddedDriver
DERBY_PROTOCOL = jdbc:derby:
We dont have multiple instance of derby. We are attaching the AccessDB and
DatabaseConnectionManager class for your reference.
[attachment "DatabaseConnectionManager.java" deleted by Sridharsingh Inder/LNTINFOTECH]
[attachment "AccessDB.java" deleted by Sridharsingh Inder/LNTINFOTECH]
Best Regards,
Sridhar
"Julius.Stroffek" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/09/2006 08:09 PM
Please respond to
[email protected]
To
[email protected]
cc
[email protected], [EMAIL PROTECTED]
Subject
Re: Query regarding derby
Hi Sridharsingh,
Please describe more your running configuration. This kind of error may occur
if you are running different instances of derby to access a same database.
Which version of derby are you running? Do you have more instances of derby on
the same machine? What exactly are you doing?
I have posted the reply to derby-user mailing list since I think it is related
more to the user issue.
Cheers
Julo
Sridharsingh Inder wrote:
Hi Derby Team,
We are using derby database in our application. While updating the table, we
are getting
"A lock could not be obtained within the time requested " this exception.
My queries are as follows
1. Why I am getting this exception?
2. What I should do to avoid this error?
3. How the locking mechanism working in Derby Database?
Thanks in Advance .
Best Regards,
Sridhar
______________________________________________________________________
______________________________________________________________________
