db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2141) BlobClob4BlobTest.testPositionBlob() fails with NullPointerException
Date Sun, 06 May 2007 15:49:15 GMT

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

Knut Anders Hatlen commented on DERBY-2141:
-------------------------------------------

> before adding the synchonization, what effect will that have on possible finalizer/synchronization
deadlock?

Depends on what we synchronize on. If we synchronize on the connection sync object, it could
definitely lead to deadlocks since we sometimes call System.runFinalization() while holding
the monitor on the object. Having a synchronized flag or something locally in BaseContainerHandle
that only prevented threads to enter close() concurrently would be safe, I think.

> BlobClob4BlobTest.testPositionBlob() fails with NullPointerException
> --------------------------------------------------------------------
>
>                 Key: DERBY-2141
>                 URL: https://issues.apache.org/jira/browse/DERBY-2141
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.3.0.0
>         Environment: Java SE 6, Java SE 5.0 (less frequently). Linux and Solaris.
>            Reporter: Knut Anders Hatlen
>         Attachments: stacktrace.diff
>
>
> Seen in the nightly regression tests:
> http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/lin/481811-org.apache.derbyTesting.functionTests.suites.All_diff.txt
> http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/lin/480626-org.apache.derbyTesting.functionTests.suites.All_diff.txt

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message