[JBoss JIRA] (DROOLS-5438) DMN align FEEL behaviour when sum([])
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5438:
--------------------------------------
Summary: DMN align FEEL behaviour when sum([])
Key: DROOLS-5438
URL: https://issues.redhat.com/browse/DROOLS-5438
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Attachments: image-2020-06-17-12-38-33-381.png
from the DMN spec !image-2020-06-17-12-38-33-381.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ]
Tristan Tarrant commented on JGRP-2484:
---------------------------------------
I can provide a backport
> SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
> -------------------------------------------------
>
> Key: JGRP-2484
> URL: https://issues.redhat.com/browse/JGRP-2484
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 5.0.0.Final
>
>
> WildFly OpenSSL provides a high-performance implementation of SSLContext.
> While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API.
> It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ]
Tristan Tarrant reassigned JGRP-2484:
-------------------------------------
Assignee: Tristan Tarrant (was: Bela Ban)
> SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
> -------------------------------------------------
>
> Key: JGRP-2484
> URL: https://issues.redhat.com/browse/JGRP-2484
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 5.0.0.Final
>
>
> WildFly OpenSSL provides a high-performance implementation of SSLContext.
> While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API.
> It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ELY-1998) IllegalStateException: unable to create JcaTlsCrypto: DEFAULT SecureRandom not available when configuring BC FIPS on JDK 11
by Diana Vilkolakova (Jira)
[ https://issues.redhat.com/browse/ELY-1998?page=com.atlassian.jira.plugin.... ]
Diana Vilkolakova commented on ELY-1998:
----------------------------------------
[~fjuma] I tried it but the exception stays the same.
> IllegalStateException: unable to create JcaTlsCrypto: DEFAULT SecureRandom not available when configuring BC FIPS on JDK 11
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1998
> URL: https://issues.redhat.com/browse/ELY-1998
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Diana Vilkolakova
> Priority: Major
>
> The below steps require ELY-1982 bugfix to work.
> Configure security providers in java.security file:
> {code}
> security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> security.provider.2=org.bouncycastle.jsse.provider.BouncyCastleJsseProvider
> security.provider.3=SUN
> {code}
> Add the bc-fips.jar and bctls-fips-1.0.10.jar to the CLASSPATH and generate keystore in JBOSS_HOME/standalone/configuration folder:
> {code}
> keytool -genkeypair -alias appserver -keyalg RSA -keysize 2048 -keypass password -keystore "fips.keystore" -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath $CLASSPATH -storetype BCFKS -storepass password -dname "CN=testserver,OU=TESTOU,O=TESTO,L=TESTL,ST=TESTCZ,C=TESTCZ" -validity 730 -v
> {code}
> Try to configure `server-ssl-context`:
> {code}
> module add --name=org.bouncycastle.fips --resources=/path/to/bc-fips-1.0.2.jar:/path/to/bctls-fips-1.0.10.jar
> /subsystem=elytron/provider-loader=bc:add(module=org.bouncycastle.fips)
> /subsystem=elytron/key-store=fipsKS:add(path=fips.keystore, relative-to=jboss.server.config.dir, credential-reference={clear-text=password}, type="BCFKS", providers=bc)
> /subsystem=elytron/key-manager=fipsKM:add(key-store=fipsKS, algorithm="X509", credential-reference={clear-text=password}, providers=bc)
> /subsystem=elytron/server-ssl-context=fipsSSC:add(key-manager=fipsKM, protocols=["TLSv1.2"], providers=bc)
> {code}
> The last command results in:
> {code}
> {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.fipsSSC" => "Failed to start service
> Caused by: java.lang.IllegalStateException: unable to create JcaTlsCrypto: DEFAULT SecureRandom not available
> Caused by: java.security.NoSuchAlgorithmException: DEFAULT SecureRandom not available"}},
> "rolled-back" => true
> }
> {code}
> The exception is happening [on this line|https://github.com/Skyllarr/wildfly-elytron/blob/ELY-1982/ssl/src/ma...] . This exception can be avoided by either using *new SecureRandom()* instead of null during initialization of sslContext, or by configuring securerandom with using *CryptoServicesRegistrar.setSecureRandom(new SecureRandom());* in code beforehand (this would require bc dependency).
> I tried to configure secure random statically by setting *securerandom.strongAlgorithms=DEFAULT:BCFIPS* in java.security or by trying to pass secure random as parameter to constructor with
> {code}
> security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider "C:DEFRND[SHA512];ENABLE{ALL};"
> {code}
> but neither had any effect. I did not find how to configure this statically for Java 11 in BC documentation.
> We could pass new instance of SecureRandom when initializing sslContext (if bouncycastle is used), or set secureRandom beforehand, or catch this exception and then use `new SecureRandom()`. But should we force the users to use SecureRandom set in the code by us? If users want to use Bouncycastle they should configure the secure random themselves since it is needed by the provider?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFCORE-5010) Startup error messages caused by expression where expressions are not allowed are confusing
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFCORE-5010?page=com.atlassian.jira.plug... ]
Lukas Vydra moved WFLY-6938 to WFCORE-5010:
-------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-5010 (was: WFLY-6938)
Component/s: Server
(was: Server)
Affects Version/s: (was: 10.1.0.CR1)
> Startup error messages caused by expression where expressions are not allowed are confusing
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-5010
> URL: https://issues.redhat.com/browse/WFCORE-5010
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Server
> Reporter: Ondrej Chaloupka
> Assignee: Lukas Vydra
> Priority: Minor
>
> When a property expression is used at place where expression usage is not allowed then error message which is shown is quite confusing. From user point of view (especially the newcomer) it would be nice if the error message shows the real reason - usage of expression at place where is not permitted.
> Maybe CLI could warn on usage of expression on place where is not allowed too.
> Documentation recommends configuration with CLI, editing of XML file is common too. More of it there are some tasks which are harder to be done with CLI and editing XML is faster/easier.
> Examples:
> Setting
> {code}
> /subsystem=ee/managed-executor-service=default:write-attribute(name=context-service, value="${my.context.service}")
> {code}
> ends with this error message during startup
> {code}
> 14:13:21,076 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ee"),
> ("managed-executor-service" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.concurrent.ee.context.service.${my.context.service}"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.concurrent.ee.executor.default is missing [jboss.concurrent.ee.context.service.${my.context.service}]"]}
> {code}
> another confusion is setting name of host in {{host-slave.xml}} file. When set as
> {code}
> <host xmlns="urn:jboss:domain:4.2" host="${host.name}">
> {code}
> then NullPointerException is thrown.
> {code}
> [Host Controller] 14:18:45,238 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188)
> at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:594)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> at java.lang.Thread.run(Thread.java:745)[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError
> at [row,col]:[3,1][Host Controller] Message: WFLYCTL0197: Unexpected attribute 'host' encountered
> at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117)
> at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:311)
> at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170)
> at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79)
> at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 4 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13515) Application does not fail when @Singleton @PostConstruct throws exception
by Panagiotis Sotiropoulos (Jira)
[ https://issues.redhat.com/browse/WFLY-13515?page=com.atlassian.jira.plugi... ]
Panagiotis Sotiropoulos reassigned WFLY-13515:
----------------------------------------------
Assignee: Cheng Fang (was: Panagiotis Sotiropoulos)
> Application does not fail when @Singleton @PostConstruct throws exception
> -------------------------------------------------------------------------
>
> Key: WFLY-13515
> URL: https://issues.redhat.com/browse/WFLY-13515
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 19.0.0.Final, 20.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
> Labels: Regression, downstream_dependency
> Attachments: helloWorld.ear
>
>
> In EAP 6.4 , sub deployments were accessible before all Singleton's PostConstruct were finished, this was fixed via [1]. After this fix if an exception was thrown from PostConstruct, then the whole deployment was in a failed state as well. EAP 7.0 works the same as EAP 6.4 after the fix.
> In EAP 7.3/7.2/7.1 when the Singleton throws an exception, the sub deployments are accessible.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1310908
> EJB 3.1 spec, section 4.8.1:
> {quote}
> If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application.
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-6938) Startup error messages caused by expression where expressions are not allowed are confusing
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFLY-6938?page=com.atlassian.jira.plugin... ]
Lukas Vydra commented on WFLY-6938:
-----------------------------------
I can confirm that host.xml part is issue no more.
As for the main one, I will move it to WFCORE and continue with better handling of capability resolution.
> Startup error messages caused by expression where expressions are not allowed are confusing
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-6938
> URL: https://issues.redhat.com/browse/WFLY-6938
> Project: WildFly
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.1.0.CR1
> Reporter: Ondrej Chaloupka
> Assignee: Lukas Vydra
> Priority: Minor
>
> When a property expression is used at place where expression usage is not allowed then error message which is shown is quite confusing. From user point of view (especially the newcomer) it would be nice if the error message shows the real reason - usage of expression at place where is not permitted.
> Maybe CLI could warn on usage of expression on place where is not allowed too.
> Documentation recommends configuration with CLI, editing of XML file is common too. More of it there are some tasks which are harder to be done with CLI and editing XML is faster/easier.
> Examples:
> Setting
> {code}
> /subsystem=ee/managed-executor-service=default:write-attribute(name=context-service, value="${my.context.service}")
> {code}
> ends with this error message during startup
> {code}
> 14:13:21,076 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "ee"),
> ("managed-executor-service" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.concurrent.ee.context.service.${my.context.service}"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.concurrent.ee.executor.default is missing [jboss.concurrent.ee.context.service.${my.context.service}]"]}
> {code}
> another confusion is setting name of host in {{host-slave.xml}} file. When set as
> {code}
> <host xmlns="urn:jboss:domain:4.2" host="${host.name}">
> {code}
> then NullPointerException is thrown.
> {code}
> [Host Controller] 14:18:45,238 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188)
> at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:594)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> at java.lang.Thread.run(Thread.java:745)[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError
> at [row,col]:[3,1][Host Controller] Message: WFLYCTL0197: Unexpected attribute 'host' encountered
> at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117)
> at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:311)
> at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170)
> at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79)
> at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 4 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5437) Unable to deploy project to kie server
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5437?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5437:
--------------------------------
Attachment: Screenshot from 2020-06-17 07-29-32.png
> Unable to deploy project to kie server
> --------------------------------------
>
> Key: DROOLS-5437
> URL: https://issues.redhat.com/browse/DROOLS-5437
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.39.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2020-06-17 07-29-32.png, c.d is undefined 2.scesim, c.d is undefined.scesim, error.log, image-2020-06-16-21-39-06-147.png, undefinedType.webm
>
>
> Cannot deploy any project to kie-server
> Kie server fails deploying project with message [^c.d is undefined.scesim] [^c.d is undefined 2.scesim]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months