July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5069) libwfssl is not detected by EAP automatically -> cannot use OpenSSL security provider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-5069?page=com.atlassian.jira.plug... ] Farah Juma updated WFCORE-5069: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/4282) > libwfssl is not detected by EAP automatically -> cannot use OpenSSL security provider > ------------------------------------------------------------------------------------- > > Key: WFCORE-5069 > URL: https://issues.redhat.com/browse/WFCORE-5069 > Project: WildFly Core > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > Looks like detection of `libwfssl` is broken in current build. When I try to configure OpenSSL security provider in legacy security, I can see following errors in standalone.log: > {code:java} > 15:39:44,704 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context: WFLYDM0018: Unable to start service15:39:44,704 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context: WFLYDM0018: Unable to start service at org.jboss.as.domain.management.security.SSLContextService.start(SSLContextService.java:116) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748)Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: openssl.TLSv1.2, provider: openssl, class: org.wildfly.openssl.OpenSSLContextSPI$OpenSSLTLS_1_2_ContextSpi) at java.security.Provider$Service.newInstance(Provider.java:1617) at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) at org.jboss.as.domain.management.security.SSLContextService.start(SSLContextService.java:105) ... 8 moreCaused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.wildfly.openssl.SSL.init(SSL.java:87) at org.wildfly.openssl.OpenSSLContextSPI.<init>(OpenSSLContextSPI.java:129) at org.wildfly.openssl.OpenSSLContextSPI$OpenSSLTLS_1_2_ContextSpi.<init>(OpenSSLContextSPI.java:484) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.security.Provider$Service.newInstance(Provider.java:1595) ... 12 moreCaused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.wildfly.openssl.SSL.init(SSL.java:82) ... 19 moreCaused by: java.lang.UnsatisfiedLinkError: no wfssl in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1860) at java.lang.Runtime.loadLibrary0(Runtime.java:870) at java.lang.System.loadLibrary(System.java:1124) at org.wildfly.openssl.SSL$LibraryLoader.load(SSL.java:288) ... 24 more > 15:39:44,818 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("core-service" => "management"), ("security-realm" => "ApplicationRealm")]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ApplicationRealm.ssl-context" => "WFLYDM0018: Unable to start service Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: openssl.TLSv1.2, provider: openssl, class: org.wildfly.openssl.OpenSSLContextSPI$OpenSSLTLS_1_2_ContextSpi) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.UnsatisfiedLinkError: no wfssl in java.library.path"}} {code} > > This is a regression against previous release - {{EAP7.3.1}}. Expected behaviour is no error in the log, libwfssl is loaded successfully and OpenSSL is correctly used for TLS connections. > Note - there has been a change in the location of the particular libwfssl native binaries in the distribution, see https://github.com/wildfly-security/wildfly-openssl/commit/c5c07d3dc0d637... > {code:title=7.3.1} > $ find . -name *wfssl* > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-sparcv9/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/win-x86_64/wfssl.dll > ./modules/system/layers/base/org/wildfly/openssl/main/lib/win-i386/wfssl.dll > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-i386/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-s390x/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-x86_64/libwfssl.so > {code} > and > {code:title=7.4.0.CD20-CR1} > $ find . -name *ssl* > ./modules/system/layers/base/org/wildfly/openssl > ./modules/system/layers/base/org/wildfly/openssl/main/wildfly-openssl-java-1.1.0.Final-redhat-00001.jar > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-sparcv9/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/solaris-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/win-x86_64/wfssl.dll > ./modules/system/layers/base/org/wildfly/openssl/main/lib/win-i386/wfssl.dll > ./modules/system/layers/base/org/wildfly/openssl/main/lib/linux-s390x/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/el8-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/el7-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/el6-x86_64/libwfssl.so > ./modules/system/layers/base/org/wildfly/openssl/main/lib/el6-i386/libwfssl.so > ./modules/system/layers/base/org/wildfly/security/elytron-private/main/wildfly-elytron-ssl-1.12.1.Final-redhat-00001.jar > {code} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5545) Cannot create KieBase - StringIndexOutOfBounds

by Ciprian Chiru (Jira)

Ciprian Chiru created DROOLS-5545: ------------------------------------- Summary: Cannot create KieBase - StringIndexOutOfBounds Key: DROOLS-5545 URL: https://issues.redhat.com/browse/DROOLS-5545 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.40.0.Final, 7.39.0.Final, 7.38.0.Final, 7.37.0.Final, 7.36.0.Final, 7.35.0.Final, 7.34.0.Final, 7.33.0.Final Reporter: Ciprian Chiru Assignee: Mario Fusco Drls no longer built. Give the rule: {code:java} package rules; import org.example.drools.model.*; import org.apache.commons.lang3.StringUtils; global java.util.Set controlSet; rule "will execute per each Measurement having ID color" no-loop when Measurement( id == "color", $colorVal : val ); then controlSet.add($colorVal); end rule "will execute per each Measurement having ID color #2" no-loop when Measurement( !(StringUtils.isNotBlank(id)), $colorVal : val ); then controlSet.add($colorVal); end rule "will execute per each Measurement having ID color #3" no-loop when Measurement( !(id != "color"), $colorVal : val ); then controlSet.add($colorVal); end{code} When the engine starts it throws: {code:java} StringIndexOutOfBounds begin 0, end -1, length 18{code} Commenting out the last rule, it works. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5544) RuleRuntimeEventListener not containing the rule that triggered it when rules are compiled

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5544?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5544: -------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > RuleRuntimeEventListener not containing the rule that triggered it when rules are compiled > ------------------------------------------------------------------------------------------ > > Key: DROOLS-5544 > URL: https://issues.redhat.com/browse/DROOLS-5544 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.31.0.Final > Reporter: Ciprian Chiru > Assignee: Mario Fusco > Priority: Major > > When rules are compiled using _kie-maven-compile_, the event handlers implementing > _RuleRuntimeEventListener_ no longer have the rule that triggered them set (_ObjectInsertedEvent.getRule()_ is null) . > > > {code:java} > public class MyListener implements RuleFactEventListener { > @Override > public void objectInserted(final ObjectInsertedEvent event) { > System.out.println(event.getRule()); // Throws exception > } > {code} > > > It only happens when the compiler plugin is invoked. If the rules are used as such, the event is properly set. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5544) RuleRuntimeEventListener not containing the rule that triggered it when rules are compiled

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5544?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-5544: ----------------------------------- Assignee: Mario Fusco (was: Luca Molteni) > RuleRuntimeEventListener not containing the rule that triggered it when rules are compiled > ------------------------------------------------------------------------------------------ > > Key: DROOLS-5544 > URL: https://issues.redhat.com/browse/DROOLS-5544 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.31.0.Final > Reporter: Ciprian Chiru > Assignee: Mario Fusco > Priority: Major > > When rules are compiled using _kie-maven-compile_, the event handlers implementing > _RuleRuntimeEventListener_ no longer have the rule that triggered them set (_ObjectInsertedEvent.getRule()_ is null) . > > > {code:java} > public class MyListener implements RuleFactEventListener { > @Override > public void objectInserted(final ObjectInsertedEvent event) { > System.out.println(event.getRule()); // Throws exception > } > {code} > > > It only happens when the compiler plugin is invoked. If the rules are used as such, the event is properly set. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13711) InfinispanRoutingProvider generates wrong service names when server name contain a dot.

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13711?page=com.atlassian.jira.plugi... ] Paul Ferraro deleted WFLY-13711: -------------------------------- > InfinispanRoutingProvider generates wrong service names when server name contain a dot. > --------------------------------------------------------------------------------------- > > Key: WFLY-13711 > URL: https://issues.redhat.com/browse/WFLY-13711 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 21.0.0.Beta1 > > > The problematic pattern: > > {code:java} > BinaryRequirement requirement = ...; > ServiceName.parse(requirement.resolve(container, cache)); > {code} > should be: > {code:java} > ServiceName.parse(requirement.getName()).append(container, cache); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13711) InfinispanRoutingProvider generates wrong service names when server name contain a dot.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13711: ----------------------------------- Summary: InfinispanRoutingProvider generates wrong service names when server name contain a dot. Key: WFLY-13711 URL: https://issues.redhat.com/browse/WFLY-13711 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 21.0.0.Beta1 The problematic pattern: {code:java} BinaryRequirement requirement = ...; ServiceName.parse(requirement.resolve(container, cache)); {code} should be: {code:java} ServiceName.parse(requirement.getName()).append(container, cache); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13710) Hibernate/JPA custom 2LC regions generate wrong service names when region names contain a dot.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13710: ----------------------------------- Summary: Hibernate/JPA custom 2LC regions generate wrong service names when region names contain a dot. Key: WFLY-13710 URL: https://issues.redhat.com/browse/WFLY-13710 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 21.0.0.Beta1 The problematic pattern: {code:java} BinaryRequirement requirement = ...; ServiceName.parse(requirement.resolve(container, cache)); {code} should be: {code:java} ServiceName.parse(requirement.getName()).append(container, cache); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5544) RuleRuntimeEventListener not containing the rule that triggered it when rules are compiled

by Ciprian Chiru (Jira)

Ciprian Chiru created DROOLS-5544: ------------------------------------- Summary: RuleRuntimeEventListener not containing the rule that triggered it when rules are compiled Key: DROOLS-5544 URL: https://issues.redhat.com/browse/DROOLS-5544 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.31.0.Final Reporter: Ciprian Chiru Assignee: Luca Molteni When rules are compiled using _kie-maven-compile_, the event handlers implementing _RuleRuntimeEventListener_ no longer have the rule that triggered them set (_ObjectInsertedEvent.getRule()_ is null) . {code:java} public class MyListener implements RuleFactEventListener { @Override public void objectInserted(final ObjectInsertedEvent event) { System.out.println(event.getRule()); // Throws exception } {code} It only happens when the compiler plugin is invoked. If the rules are used as such, the event is properly set. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5543) [Guided Decision Table Editor] Pressing <tab> to exit cell throws client-side exception

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5543?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5543: ----------------------------------- Attachment: DROOLS-5543.png > [Guided Decision Table Editor] Pressing <tab> to exit cell throws client-side exception > --------------------------------------------------------------------------------------- > > Key: DROOLS-5543 > URL: https://issues.redhat.com/browse/DROOLS-5543 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.41.0.Final > Reporter: Michael Anstis > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, regression > Attachments: DROOLS-5543.png > > > Pressing <tab> to exit a cell in a Guided Decision Table throws a client-side exception. > See the attached screenshot. Pressing <tab> in the {{Fred}} cell throws the exception. > Clicking outside of it (to loose focus) is OK. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5543) [Guided Decision Table Editor] Pressing <tab> to exit cell throws client-side exception

by Michael Anstis (Jira)

Michael Anstis created DROOLS-5543: -------------------------------------- Summary: [Guided Decision Table Editor] Pressing <tab> to exit cell throws client-side exception Key: DROOLS-5543 URL: https://issues.redhat.com/browse/DROOLS-5543 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.41.0.Final Reporter: Michael Anstis Assignee: Toni Rikkola Pressing <tab> to exit a cell in a Guided Decision Table throws a client-side exception. See the attached screenshot. Pressing <tab> in the {{Fred}} cell throws the exception. Clicking outside of it (to loose focus) is OK. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020