Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

synchronized should be used for final map consumers other than method parameter consumer. #54

Merged
merged 1 commit into from
Oct 9, 2016

Conversation

henng
Copy link
Contributor

@henng henng commented Oct 8, 2016

Motivation

synchronized should be used for final map consumers other than method parameter consumer.

Modifications

-        synchronized (consumer) {
+        synchronized (consumers) {

Result

synchronized works correctly.

synchronized should be used for final map 'consumers' other than method parameter 'consumer'.
@yahoocla
Copy link

yahoocla commented Oct 8, 2016

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! 😄

@yahoocla
Copy link

yahoocla commented Oct 8, 2016

CLA is valid!

@henng henng changed the title Update PulsarClientImpl.java synchronized should be used for final map consumers other than method parameter consumer. Oct 8, 2016
@merlimat merlimat added this to the 1.15 milestone Oct 9, 2016
@merlimat merlimat added type/bug The PR fixed a bug or issue reported a bug area/client labels Oct 9, 2016
Copy link
Contributor

@merlimat merlimat left a comment

Choose a reason for hiding this comment

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

Thanks!

@merlimat merlimat merged commit cc7c807 into apache:master Oct 9, 2016
sijie added a commit to sijie/pulsar that referenced this pull request Mar 4, 2018
* Refactor to support at-least-once processing

This change is refactoring the relationship between Spawner, FunctionContainer and JavaInstance to better support various processing semantics.

- ThreadFunctionContainerFactory is a "singleton" across multiple functions.
- Spawner, FunctionContainer and JavaInstance are per function. Spawner is manging the lifecycle of function container, in the function container
  it will folks a thread for running java instance, because it has to load classpathes correctly.
- Remove subscribermanager and move consumer and producer logic into container. that means in future if we are supporting process based and docker
  based container, we can just take the thread container and run it directly as a separate process or a separate docker process. There is no
  extra communication between spawner and containers.

* Create pulsar client in thread container factory
hrsakai pushed a commit to hrsakai/pulsar that referenced this pull request Dec 10, 2020
* [Issue:53]Fix concurrent map write

Signed-off-by: xiaolong.ran <ranxiaolong716@gmail.com>
hangc0276 pushed a commit to hangc0276/pulsar that referenced this pull request May 26, 2021
Tries to Provided a Tenant name in tests to make the tests more clear.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/client type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants