[
https://issues.apache.org/jira/browse/DERBY-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932127#comment-13932127
]
Myrna van Lunteren commented on DERBY-6506:
-------------------------------------------
Except in very rare cases deadlocks are a result of, or can be addressed by
changes in, application design.
Analyzing the derby.log will help to identify where the problems are.
Make sure you run with the following details in your derby.properties:
derby.language.logStatementText=true
derby.infolog.append=true
derby.stream.error.logSeverityLevel=0
(derby.properties is a text file that you can create yourself if it does not
exist; it needs to live in the directory where you start the JVM that starts
derby (usually where you find derby.log)).
> Deadlock issues with Derby when using multithreading in Netcool Impact
> ----------------------------------------------------------------------
>
> Key: DERBY-6506
> URL: https://issues.apache.org/jira/browse/DERBY-6506
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.2.2
> Reporter: Shefali Sampat
> Fix For: 10.8.2.2
>
>
> Customer is using Derby embedded in Netcool Impact 6.1.1. Customer has
> created custom tables in the DB. When using multithreading and sending a lot
> of events, customer is noticing deadlock issues. The deadlock clears up after
> some time. Customer enabled row locking instead of table locking but still
> the same issue occurs. Please contact Shefali Sampat (Impact L3) at
> [email protected] for further info or if u need to look at the derby logs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
