Skip to content

Fix synchronization on _matched#504

Open
toad wants to merge 1 commit intohyphanet:nextfrom
toad:message-filter-concurrency-fixes
Open

Fix synchronization on _matched#504
toad wants to merge 1 commit intohyphanet:nextfrom
toad:message-filter-concurrency-fixes

Conversation

@toad
Copy link
Contributor

@toad toad commented Feb 24, 2016

This might have been valid originally but broke because of adding asynchronous filters.

This was probably valid originally but broke because of adding
asynchronous filters.
@bertm
Copy link
Contributor

bertm commented Mar 15, 2016

If _matched posed a problem, _message is problematic as well. getMessage should then also be synchronized on this.
(and so should effectively all users of all other member variables be synchronized, although they are not as important as they appear to be of less use to set asynchronously)

@toad
Copy link
Contributor Author

toad commented Mar 15, 2016

Really this needs refactoring so we use another object and can make stuff final. One serious concern is that it can call callbacks inside methods that ought to have more locking!

@nextgens
Copy link
Contributor

nextgens commented Jul 9, 2016

Can't we use ThreadLocal for that?

@hernic
Copy link
Contributor

hernic commented May 6, 2024

@nextgens @bertm Can you validate that this PR is mergeable as is and create another Issue for a potentiel other target (#504 (comment)) and for a ThreadLocal solution (#504 (comment)) ?

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