[
https://issues.apache.org/jira/browse/DERBY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3379:
-----------------------------------
Attachment: derby-3379-1a-enforce_no_chaining.stat
derby-3379-1a-enforce_no_chaining.diff
'derby-3379-1a-enforce_no_chaining.diff' is an attempt to fix both the NPE and
the bug hiding underneath.
The basic strategy is to make sure the last DSS has the chaining bits set to no
chaining when endWriteChain is called and the data is flushed (sent over the
wire).
I am not sure if this is the best approach, but it fixes the bug. I have run
suites.All successfully with an earlier version of the patch, and I'm now
running both derbyall and suites.All with this version to confirm that nothing
breaks.
Patch is ready for review, but not for commit. There is an unnecessary method
rename in there that will go into a separate commit.
> "No Current connection" on PooledConnection.getConnection() if pooled
> connection is reused during connectionClosed processing
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3379
> URL: https://issues.apache.org/jira/browse/DERBY-3379
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1
> Reporter: Kathey Marsden
> Attachments: derby-3379-1a-enforce_no_chaining.diff,
> derby-3379-1a-enforce_no_chaining.stat
>
>
> This is the client version of bug DERBY-2142. It can be reproduced by
> enabling the test, DataSourceTest.testPooledReuseOnClose() for client. I am
> opening a new issue for client as the embedded fix was backported to 10.1 and
> I am guessing the client fix won't be backported that far. Better to keep it
> as a separate issue.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
