[JBoss JIRA] (WFCORE-2924) Unclear model description of max-pool-size attribute in IO subsystem
by Romain Pelisse (JIRA)
Romain Pelisse created WFCORE-2924:
--------------------------------------
Summary: Unclear model description of max-pool-size attribute in IO subsystem
Key: WFCORE-2924
URL: https://issues.jboss.org/browse/WFCORE-2924
Project: WildFly Core
Issue Type: Bug
Components: IO
Affects Versions: 3.0.0.Beta24
Reporter: Romain Pelisse
Assignee: Romain Pelisse
Priority: Minor
{code:java}
/subsystem=io/worker=*:read-attribute(name=max-pool-size)
{code}
Current model description: "Max worker pool size"
Suggested improvement: "The maximum number of threads to allow in the underlying java.util.concurrent.ThreadPoolExecutor. When this limit is reached, tasks which cannot be queued are rejected."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JGRP-2173) Add more bundler stats
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2173?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2173.
----------------------------
Resolution: Done
> Add more bundler stats
> ----------------------
>
> Key: JGRP-2173
> URL: https://issues.jboss.org/browse/JGRP-2173
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0.4
>
>
> Add stats to TransferQueueBundler (and possibly other bundlers, too):
> * Average fill count (number of bytes, {{count}}) when a batch was sent
> * Average number of messages in the (main) queue when a batch was sent
> * Number of times a batch was sent because {{max_bundler_size}} was exceeded
> * Number of times a batch was sent because no more messages were received
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1605) Ability to run TCK tests during DMN build
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-1605:
-------------------------------------
Summary: Ability to run TCK tests during DMN build
Key: DROOLS-1605
URL: https://issues.jboss.org/browse/DROOLS-1605
Project: Drools
Issue Type: Enhancement
Components: dmn engine
Affects Versions: 7.1.0.Beta2
Reporter: Tibor Zimányi
Assignee: Tibor Zimányi
Fix For: 7.1.0.Beta3
We should be able to run DMN-TCK tests as part of our build, so we can quickly find bugs and compliance problems while developing new features.
I will provide PR for this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers
by John Mazzitelli (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugi... ]
John Mazzitelli edited comment on WFCORE-2526 at 6/6/17 9:33 AM:
-----------------------------------------------------------------
Right, I am putting things in HOST_CONTROLLER_JAVA_OPTS in the .conf.
What you proposed sounds like a good solution for my use-case ("-Dserver-excluded-properties")
was (Author: mazz):
Right, I am putting things in HOST_CONTROLLER_JAVA_OPTS in the .conf.
What you proposed sounds like a good solution for my use-case ("--server-excluded-properties")
> Domain mode passed unwanted sys props to spawned servers
> --------------------------------------------------------
>
> Key: WFCORE-2526
> URL: https://issues.jboss.org/browse/WFCORE-2526
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: John Mazzitelli
> Priority: Critical
> Fix For: 3.0.0.Beta25
>
>
> This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props.
> I would say the solution should involve any properties, not just jboss.server.xxx properties.
> In my case, I'm trying to inject a javaagent into the host controller but I do NOT want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL) I'm forced to pass in "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and
> "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host controller can start up.
> But these gets passed to the spawned servers and causes them to fail to boot up (because while my -javaagent command line argument isn't passed to their JVM, the -D sys props are and those combination of sys props are deadly without a JUL-enabled javaagent).
> See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7664) Missing default values in ldap-key-store description in management model.
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFLY-7664?page=com.atlassian.jira.plugin.... ]
Yeray Borges reassigned WFLY-7664:
----------------------------------
Assignee: Yeray Borges (was: Darran Lofthouse)
> Missing default values in ldap-key-store description in management model.
> -------------------------------------------------------------------------
>
> Key: WFLY-7664
> URL: https://issues.jboss.org/browse/WFLY-7664
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Yeray Borges
> Labels: user_experience
> Fix For: 11.0.0.Beta1
>
>
> Some attributes of Elytron {{ldap-key-store}} resource have defined some default value, but description of these attributes in CLI is missing default values. According to XSD following attributes of {{ldap-key-store}} have assigned some default value:
> * {{search-recursive}} has default value {{true}}
> * {{search-time-limit}} has default value {{10000}}
> * {{filter-alias}} has default value {{(alias-attribute=\{0\})}}
> * {{filter-certificate}} has default value {{(certificate-attribute=\{0\})}}
> * {{filter-iterate}} has default value {{(alias-attribute=*)}}
> * {{alias-attribute}} has default value {{cn}}
> * {{certificate-attribute}} has default value {{usercertificate}}
> * {{certificate-type}} has default value {{X.509}}
> * {{certificate-chain-attribute}} has default value {{userSMIMECertificate}}
> * {{certificate-chain-encoding}} has default value {{PKCS7}}
> * {{key-attribute}} has default value {{userPKCS12}}
> * {{key-type}} has default value {{PKCS12}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month