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
ISPN-9422 Remove Worker Threads property #6773
ISPN-9422 Remove Worker Threads property #6773
Conversation
@tristantarrant There are a few related test failures |
@tristantarrant What's up with this? |
It looks like the |
ef3a761
to
069f140
Compare
069f140
to
9916b7d
Compare
Failures are unrelated |
public static final AttributeDefinition<AdminOperationsHandler> ADMIN_OPERATION_HANDLER = AttributeDefinition.builder("admin-operation-handler", null, AdminOperationsHandler.class).immutable().build(); | ||
public static final AttributeDefinition<Boolean> ZERO_CAPACITY_NODE = AttributeDefinition.builder("zero-capacity-node", false).immutable().build(); | ||
|
||
// The default value can be overridden so it is the responsibility of each protocol to add it to the set | ||
public static final AttributeDefinition<Integer> WORKER_THREADS = AttributeDefinition.builder("worker-threads", 1).immutable().build(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we keep the attribute definition in the base class at all? It's not very clear why the Memcached and REST servers should have only 1 worker thread, if each had its own definition it could also have a comment explaining the choice.
- Also ensure that different default worker thread defaults don't pollute the others
9916b7d
to
6d207f3
Compare
https://issues.jboss.org/browse/ISPN-9422
I've also made sure that different endpoints can actually have different defaults