[
https://issues.apache.org/jira/browse/DERBY-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2141:
----------------------------------
As you point out, performance of close may not be much of an issue. I was
taking the leap that there may be more problems
with OverflowInputStream than close. I am just not sure if it is our job or
the calling code to fix them. Should we prevent a
client jdbc app from calling any interface on a single OverflowInputStream from
2 threads at the same time (for example read)?
Also I don't understand the issue enough, does this fix have to happen in
BaseContainerHandle? It seems reasonable to add
extra synchronization to OverflowInputStream as we hand that out of the jdbc
layer to direct callers, but if we start changing the
classes only indirectly called I think we may not know where to stop.
> 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.
