You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/04/21 23:37:14 UTC

[jira] [Commented] (DERBY-6506) Deadlock issues with Derby when using multithreading in Netcool Impact

    [ https://issues.apache.org/jira/browse/DERBY-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976077#comment-13976077 ] 

Myrna van Lunteren commented on DERBY-6506:
-------------------------------------------

The problem was *not* that of DERBY-6011. In that case, it is most likely an application/implementation problem. 

> 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 shefali@us.ibm.com for further info or if u need to look at the derby logs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)