db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dag.wan...@oracle.com (Dag H. Wanvik)
Subject Re: Deadlock problem with Derby 10.8.2.2 in production
Date Mon, 14 May 2012 19:12:10 GMT
"Bergquist, Brett" <BBergquist@canoga.com> writes:

> In our production environment, a deadlock occurred.   The problem was triggered by some
problem in derby, but unfortunately, the error message returned to the client is:
>
> [#|2012-05-10T08:10:47.761-0400|WARNING|sun-appserver2.1|org.eclipse.persistence.session.file:/opt/canoga/canogaview/glassfish/domains/domain1/applications/j2ee-apps/csem/csem-core-api.jar-csem-PU|_ThreadID=66;_ThreadName=PMCollectionActivationManager.samResetDetected;_RequestID=9e8852a5-9136-4096-94b1-b3ccbf95d810;|
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 1.1.3.v20091002-r5404):
org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ001,
SQLERRMC: java.lang.NullPointerException  XJ001.U

Do you have access to derby.log at the time this happens?  

Of the server sessions threads DRDAConnThreads (597): 555 are cached on
waiting on the server side waiting to start servering new sessions, 42
seem to be involved in current connections (blocked on socket
read). Looks normal..

Dag

Mime
View raw message