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

Use custom thread factory on RecoveryAware connection / channel manager #33

Merged
merged 1 commit into from
Mar 13, 2015
Merged

Use custom thread factory on RecoveryAware connection / channel manager #33

merged 1 commit into from
Mar 13, 2015

Conversation

vikinghawk
Copy link
Contributor

Uplift RecoveryAwareAMQConnection and RecoveryAwareChannelManager to use ConnectionFactory's custom threadFactory. Also, get the current SecurityManager instead of
creating a new one in Environment.isAllowedToModifyThreads()

https://groups.google.com/forum/#!topic/rabbitmq-users/JteMdVaaPho

custom threadFactory. Also, get SecurityManager from System instead of
creating a new one in Environment class
michaelklishin added a commit that referenced this pull request Mar 13, 2015
Use custom thread factory on RecoveryAware connection / channel manager
@michaelklishin michaelklishin merged commit c998e0c into rabbitmq:master Mar 13, 2015
@michaelklishin michaelklishin self-assigned this Mar 13, 2015
@michaelklishin michaelklishin added this to the 3.6.0 milestone Mar 13, 2015
@michaelklishin
Copy link
Member

We'll see if we want to include this into 3.5.x. Thank you!

@vikinghawk
Copy link
Contributor Author

+1 to 3.5.x.

Thanks!

@michaelklishin
Copy link
Member

Cherry-picked to stable, will be in 3.5.1.

@vikinghawk vikinghawk deleted the threadFactory branch March 13, 2015 16:35
@dumbbell dumbbell modified the milestones: 3.5.1, 3.6.0 Mar 23, 2015
stream-iori pushed a commit to stream-iori/rabbitmq-java-client that referenced this pull request Mar 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants