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-3379) "No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing
Date Fri, 15 Feb 2008 12:56:08 GMT

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

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

I think the approach is OK, although it sounds better if the chaining bits were set correctly
in the first place. It's not quite clear to me where/how the chaining bits are set the first
time, but if I understand correctly, Statement.flowCloseOutsideUOW() will only be called if
nothing needs to be sent to the server on Statement.close(). Could we somehow use this to
send a flag down the call tree so that the chaining bits are set correctly?

Should previousUsedDssMark have been reset in clearBuffer()?

Should endDssChain() also check that (dssLengthLocation_ == offset_) so that we're completely
sure the last DSS is empty/missing?

> "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
>            Assignee: Kristian Waagan
>         Attachments: derby-3379-1a-enforce_no_chaining.diff, derby-3379-1a-enforce_no_chaining.diff,
derby-3379-1a-enforce_no_chaining.stat, derby-3379-1a-enforce_no_chaining.stat, derby-3379-1b-enforce_no_chaining.diff,
derby-3379-1c-enforce_no_chaining.diff, derby-3379-1c-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.


Mime
View raw message