[JBoss JIRA] (WFLY-10090) [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-10090?page=com.atlassian.jira.plugin... ]
Miroslav Novak moved JBEAP-14473 to WFLY-10090:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-10090 (was: JBEAP-14473)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: JMS)
Target Release: (was: 7.backlog.GA)
> [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10090
> URL: https://issues.jboss.org/browse/WFLY-10090
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Setting client globalThreadPoolSize for configuring max number of ActiveMQ-client-global-threads using system property or in connection factory which is looked up by standalone JMS client is ignored. There is alway 8 * number CPU cores.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JGRP-2259) Configurator.removeDeprecatedProperties(...) should check for @Deprecated
by Paul Ferraro (JIRA)
Paul Ferraro created JGRP-2259:
----------------------------------
Summary: Configurator.removeDeprecatedProperties(...) should check for @Deprecated
Key: JGRP-2259
URL: https://issues.jboss.org/browse/JGRP-2259
Project: JGroups
Issue Type: Bug
Reporter: Paul Ferraro
Assignee: Bela Ban
Configurator.removeDeprecatedProperties(...) removes and logs warnings for any configuration properties annotated with @DeprecatedProperty. However, this annotation is no longer in use anywhere. However, deprecated properties are consistently annotated with @Deprecated, and thus should be detected as such.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-1970) [DMN Editor] Hit policies
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1970?page=com.atlassian.jira.plugi... ]
Jozef Marko resolved DROOLS-1970.
---------------------------------
Resolution: Done
> [DMN Editor] Hit policies
> -------------------------
>
> Key: DROOLS-1970
> URL: https://issues.jboss.org/browse/DROOLS-1970
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.1.0.Beta2
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: reported-by-qe
>
> Implement hit policies of the DMN Specification:
> - Unique (Single hit policy)
> -- No overlap is possible and all rules are disjoint. Only a single rule can be matched. This is the default.
> - First (Single hit policy)
> -- Multiple (overlapping) rules can match, with different output entries. The first hit by rule order is returned (and
> evaluation can halt). This is still a common usage, because it resolves inconsistencies by forcing the first hit.
> However, first hit tables are not considered good practice because they do not offer a clear overview of the decision
> logic. It is important to distinguish this type of table from others because the meaning depends on the order of the
> rules. The last rule is often the catch-remainder. Because of this order, the table is hard to validate manually and
> therefore has to be used with care.
> - Priority (Single hit policy)
> -- Multiple rules can match, with different output entries. This policy returns the matching rule with the
> highest output priority. Output priorities are specified in the ordered list of output values, in decreasing order of
> priority. Note that priorities are independent from rule sequence.
> - Any (Single hit policy)
> -- There may be overlap, but all of the matching rules show equal output entries for each output, so any match can
> be used. If the output entries are non-equal, the hit policy is incorrect and the result is undefined.
> - Output Order (Multiple hit policy)
> -- returns all hits in decreasing output priority order. Output priorities are specified in the ordered list of
> output values in decreasing order of priority.
> - Rule Order (Multiple hit policy)
> -- Returns all hits in rule order. Note: the meaning may depend on the sequence of the rules.
> - Collect ( Multple hit policy with the aggregation operators +, >, < and #)
> -- Returns all hits in arbitrary order. An operator (‘+’, ‘<’, ‘>’, ‘#’) can be added to apply a simple function to the outputs. If no operator is present, the result is the list of all the output entries. Collect operators are:
> a) + (sum): the result of the decision table is the sum of all the distinct outputs.
> b) < (min): the result of the decision table is the smallest value of all the outputs.
> c) > (max): the result of the decision table is the largest value of all the outputs.
> d) # (count): the result of the decision table is the number of distinct outputs.
> Other policies, such as more complex manipulations on the outputs, can be performed by post-processing the
> output list (outside the decision table).
> Please ensure that the HIT policy can be changed whenever during modeling the decision table.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-1970) [DMN Editor] Hit policies
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1970?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-1970:
--------------------------------
Fix Version/s: 7.7.0.Final
> [DMN Editor] Hit policies
> -------------------------
>
> Key: DROOLS-1970
> URL: https://issues.jboss.org/browse/DROOLS-1970
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.1.0.Beta2
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: reported-by-qe
> Fix For: 7.7.0.Final
>
>
> Implement hit policies of the DMN Specification:
> - Unique (Single hit policy)
> -- No overlap is possible and all rules are disjoint. Only a single rule can be matched. This is the default.
> - First (Single hit policy)
> -- Multiple (overlapping) rules can match, with different output entries. The first hit by rule order is returned (and
> evaluation can halt). This is still a common usage, because it resolves inconsistencies by forcing the first hit.
> However, first hit tables are not considered good practice because they do not offer a clear overview of the decision
> logic. It is important to distinguish this type of table from others because the meaning depends on the order of the
> rules. The last rule is often the catch-remainder. Because of this order, the table is hard to validate manually and
> therefore has to be used with care.
> - Priority (Single hit policy)
> -- Multiple rules can match, with different output entries. This policy returns the matching rule with the
> highest output priority. Output priorities are specified in the ordered list of output values, in decreasing order of
> priority. Note that priorities are independent from rule sequence.
> - Any (Single hit policy)
> -- There may be overlap, but all of the matching rules show equal output entries for each output, so any match can
> be used. If the output entries are non-equal, the hit policy is incorrect and the result is undefined.
> - Output Order (Multiple hit policy)
> -- returns all hits in decreasing output priority order. Output priorities are specified in the ordered list of
> output values in decreasing order of priority.
> - Rule Order (Multiple hit policy)
> -- Returns all hits in rule order. Note: the meaning may depend on the sequence of the rules.
> - Collect ( Multple hit policy with the aggregation operators +, >, < and #)
> -- Returns all hits in arbitrary order. An operator (‘+’, ‘<’, ‘>’, ‘#’) can be added to apply a simple function to the outputs. If no operator is present, the result is the list of all the output entries. Collect operators are:
> a) + (sum): the result of the decision table is the sum of all the distinct outputs.
> b) < (min): the result of the decision table is the smallest value of all the outputs.
> c) > (max): the result of the decision table is the largest value of all the outputs.
> d) # (count): the result of the decision table is the number of distinct outputs.
> Other policies, such as more complex manipulations on the outputs, can be performed by post-processing the
> output list (outside the decision table).
> Please ensure that the HIT policy can be changed whenever during modeling the decision table.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9969) JDK9 + FIPS BC, unable to configure
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-9969?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-9969:
------------------------------------
It can be simplified:
- Once MODULES-349 will be inplace
- Once {{--module-path boot-modules}} will be applied on server boot
> JDK9 + FIPS BC, unable to configure
> -----------------------------------
>
> Key: WFLY-9969
> URL: https://issues.jboss.org/browse/WFLY-9969
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Final
> Reporter: Martin Choma
>
> * Configure BouncyCastleFipsProvider in java
> {code:title=$\{jdk9_home\}/conf/security/java.security}
> security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> security.provider.2=SUN
> security.provider.3=SunRsaSign
> security.provider.4=SunEC
> security.provider.5=SunJSSE BCFIPS
> security.provider.6=SunJCE
> security.provider.7=SunJGSS
> security.provider.8=SunSASL
> security.provider.9=XMLDSig
> security.provider.10=SunPCSC
> security.provider.11=JdkLDAP
> security.provider.12=JdkSASL
> security.provider.13=SunPKCS11
> {code}
> * configure -cp of java process based on https://docs.oracle.com/javase/9/security/howtoimplaprovider.htm#JSSEC-GU.... It means in $\{jboss_home\}/bin/standalone.conf put -cp option with bcfips jar
> {{JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar"}}
> * Configure additional logging
> {code}
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> /subsystem=logging/logger=org.wildfly.extension.elytron:add(level=ALL)
> {code}
> * Run CLI command usink BCFKS key store type
> {{/subsystem=elytron/key-store=bcfks_keystore:add(path=keystore.bcfks,relative-to=jboss.server.config.dir, type="BCFKS", credential-reference=\{clear-text=password\})}}
> * For some reason BouncyCastleFipsProvider is not listed among providers returned by Security.getProviders() and therefore BCFKS can't be resolved
> {code}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/mchoma/eap/7.2.0.EL12.CR1/jboss-eap-7.2
> JAVA: /opt/java/jdk-9.0.1_bcfips/bin/java
> JAVA_OPTS: -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
> =========================================================================
> ...
> 09:20:16,630 TRACE [org.wildfly.extension.elytron] (MSC service thread 1-3) No provider identified for name [null] and algorithm [BCFKS] between [SUN version 9, ApacheXMLDSig version 2.11, SunRsaSign version 9, SunEC version 9, SunJSSE version 9, SunJCE version 9, SunJGSS version 9, SunSASL version 9, XMLDSig version 9, SunPCSC version 9, JdkLDAP version 9, JdkSASL version 9, SunPKCS11 version 9, SunDeploy-MozillaJSS version 1.5, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
> 09:20:16,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.key-store.bcfks_keystore: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.bcfks_keystore: WFLYELY00004: Unable to start the service.
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:148)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'BCFKS'
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.resolveProvider(KeyStoreService.java:156)
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:110)
> ... 8 more
> {code}
> * With same java I can run succesfully this java code
> {code:java|title=TestBCLoaded.java}
> import java.security.*;
> public class TestBCLoaded {
> public static void main(String[] args) {
> Provider p = Security.getProvider("org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BCFIPS");
> if (p==null){
> System.out.println("Not Loaded: BCFIPS");
> } else {
> System.out.println("Provider name is " + p.getName());
> System.out.println("Provider version # is " + p.getVersion());
> System.out.println("Provider info is " + p.getInfo());
> }
> }
> }
> {code}
> {code}
> [mchoma@localhost jdk9Test]$ java -cp .:/home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar TestBCLoaded
> Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> Not Loaded: BouncyCastleFipsProvider
> Provider name is BCFIPS
> Provider version # is 0.9
> Provider info is BouncyCastle Security Provider (FIPS edition) v0.90
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month