Skip to content

Conversation

@gkorland
Copy link
Contributor

Move dataSource reset before connection returned to pool.
If datasource reset after the connection returned to pool, it might reset the datasource after it was allocated to another thread

Move dataSource reset before connection returned to pool.
If datasource reset after the connection returned to pool, it might reset the datasource after it was allocated to another thread
@gkorland gkorland added this to the 3.0.1 milestone Dec 17, 2018
@gkorland gkorland self-assigned this Dec 17, 2018
Copy link
Contributor

@sazzad16 sazzad16 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@gkorland gkorland merged commit 1e536e8 into master Dec 18, 2018
@gkorland gkorland deleted the gkorland-dataSource-reset branch December 18, 2018 07:35
@gkorland gkorland modified the milestones: 3.0.1, 2.10.1 Dec 25, 2018
gkorland added a commit that referenced this pull request Dec 25, 2018
@kutzi
Copy link
Contributor

kutzi commented Dec 28, 2018

In the absence of any memory barrier on the dataSource field this fixes IMHO nothing.
See 02f2cc5#r31795161

gkorland added a commit that referenced this pull request Jan 17, 2019
sazzad16 pushed a commit that referenced this pull request Jan 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants