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

JBRULES-3663 - using static thread pool and updating dispose logic #152

Closed
wants to merge 1 commit into from
Closed

JBRULES-3663 - using static thread pool and updating dispose logic #152

wants to merge 1 commit into from

Conversation

calbazasebastian
Copy link

No description provided.

@ghost ghost assigned mrietveld Oct 25, 2012
@mariofusco
Copy link
Contributor

The request is valid, but the patch needs to be improved: initializing a thread pool as a static instance is to ask for trouble and also, the use of system property alone is not consistent with our architecture. We need the pool to be created per kbase or externally but not statically and the configuration in a similar way to other drools configurations. It would be great if you could send another pull request that follows these advices.

@mariofusco mariofusco closed this Mar 6, 2013
@mrietveld
Copy link
Contributor

Sebi, FYI: my sincere apologies for not getting to this in the last 5 months. :( Mario is now actively looking at it though (thank you Mario!).

dupliaka pushed a commit to dupliaka/drools that referenced this pull request Apr 1, 2022
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.

None yet

3 participants