db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: org.apache.derby.client.am.SqlException: A lock
Date Wed, 30 Apr 2008 21:43:49 GMT
Hi Shaoyong,

For tips on how to avoid deadlocks, please see the "Deadlocks" section 
of the Derby Developer's Guide: 
http://db.apache.org/derby/docs/10.3/devguide/

Hope this helps,
-Rick

Shaoyong Wang wrote:
>
> We are using Derby 10.3.1.4. Occasionally, we saw the following error. 
> Can anybody tell me how to tune Derby to get around this? Thanks.
>
> Caused by: org.apache.derby.client.am.SqlException: A lock could not 
> be obtained due to a deadlock, cycle of locks and waiters is:
>
> …
>
> The selected victim is XID : 2057595.
>
> at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
>
> at 
> org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown 
> Source)
>
> at org.apache.derby.client.net.NetStatementReply.readExecute(Unknown 
> Source)
>
> at org.apache.derby.client.net.StatementReply.readExecute(Unknown Source)
>
> at 
> org.apache.derby.client.net.NetPreparedStatement.readExecute_(Unknown 
> Source)
>
> at org.apache.derby.client.am.PreparedStatement.readExecute(Unknown 
> Source)
>
> at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown 
> Source)
>
> at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown 
> Source)
>
> ... 79 more
>


Mime
View raw message