[
https://issues.apache.org/jira/browse/DERBY-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-6506.
---------------------------------------
Resolution: Not a Problem
Bug behavior facts: Seen in production
Marking 'Seen in production'.
Resolving as 'Not A Problem' (in Derby source, that is), because this was not
due to a specific bug in Derby. Derby was correctly identifying a problem with
the application/usage.
> 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
> Assignee: Myrna van Lunteren
> 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)
