January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4801) RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

by Vinoth Kumar Natarajan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4801?page=com.atlassian.jira.plug... ] Vinoth Kumar Natarajan updated WFCORE-4801: ------------------------------------------- Affects Version/s: 9.0.1.Final > RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used > ------------------------------------------------------------------------------------- > > Key: WFCORE-4801 > URL: https://issues.redhat.com/browse/WFCORE-4801 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 9.0.1.Final > Reporter: Vinoth Kumar Natarajan > Priority: Major > > Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory. > Analysis of the heap dump indicate that, > * All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint. > * All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli. > Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects. > To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes. > *Wildfly version details:* > bash-4.4# ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect > [standalone@localhost:9990 /] version > JBoss Admin Command-line Interface > JBOSS_HOME: /ericsson/3pp/wildfly > Release: 9.0.1.Final > Product: WildFly Full 17.0.0.Final > JAVA_HOME: /usr/ > java.version: 1.8.0_222 > java.vm.vendor: IcedTea > java.vm.version: 25.222-b10 > os.name: Linux > os.version: 4.12.14-197.15-default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13000) Put an end to problems with Jackson caused by jaxrs subsystem

by Dominik Derwiński (Jira)

[ https://issues.redhat.com/browse/WFLY-13000?page=com.atlassian.jira.plugi... ] Dominik Derwiński updated WFLY-13000: ------------------------------------- Description: There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: {noformat} java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' {noformat} or {noformat} java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) {noformat} Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? Found these on the net while trying to solve my issue: http://alloutfornoloss.com/exclude-jackson-module-wildfly/ https://stackoverflow.com/questions/37616096/wildfly-10-how-to-use-a-newe... https://stackoverflow.com/questions/38173460/dependency-conflict-loading-... https://stackoverflow.com/questions/47838240/jboss-resteasy-custom-jackso... https://stackoverflow.com/questions/56780117/unknown-conflict-causing-jav... https://stackoverflow.com/questions/20683843/jackson-annotations-ignored-... https://dzone.com/articles/jboss-modules-suck-it%E2%80%99s https://forum.camunda.org/t/camunda-json-marshalling-and-jsonignore/271/18 was: There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: {noformat} java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' {noformat} or {noformat} java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) {noformat} Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? > Put an end to problems with Jackson caused by jaxrs subsystem > ------------------------------------------------------------- > > Key: WFLY-13000 > URL: https://issues.redhat.com/browse/WFLY-13000 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 18.0.1.Final > Reporter: Dominik Derwiński > Assignee: Alessio Soldano > Priority: Major > > There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: > {noformat} > java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' > {noformat} > or > {noformat} > java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) > {noformat} > Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? > Found these on the net while trying to solve my issue: > http://alloutfornoloss.com/exclude-jackson-module-wildfly/ > https://stackoverflow.com/questions/37616096/wildfly-10-how-to-use-a-newe... > https://stackoverflow.com/questions/38173460/dependency-conflict-loading-... > https://stackoverflow.com/questions/47838240/jboss-resteasy-custom-jackso... > https://stackoverflow.com/questions/56780117/unknown-conflict-causing-jav... > https://stackoverflow.com/questions/20683843/jackson-annotations-ignored-... > https://dzone.com/articles/jboss-modules-suck-it%E2%80%99s > https://forum.camunda.org/t/camunda-json-marshalling-and-jsonignore/271/18 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13000) Put an end to problems with Jackson caused by jaxrs subsystem

by Dominik Derwiński (Jira)

Dominik Derwiński created WFLY-13000: ---------------------------------------- Summary: Put an end to problems with Jackson caused by jaxrs subsystem Key: WFLY-13000 URL: https://issues.redhat.com/browse/WFLY-13000 Project: WildFly Issue Type: Feature Request Components: REST Affects Versions: 18.0.1.Final Reporter: Dominik Derwiński Assignee: Alessio Soldano There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: {noformat} java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' {noformat} or {noformat} java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) {noformat} Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ] Yeray Borges commented on WFCORE-4764: -------------------------------------- Thanks [~harald.pehl] np, indeed, I was going to ask you to wait a bit more before start your review. I'm still working on a wildfly-core oriented solution for HAL-1653, I have something already but not 100% satisfied yet with the solution. Keep in mind that HAL-1653 could be related when if you are testing WFCORE-4764, so please, wait a bit more to have both solutions as PR before checking on your side HAL. > Availability of web console during the startup of the Domain Controller > ----------------------------------------------------------------------- > > Key: WFCORE-4764 > URL: https://issues.redhat.com/browse/WFCORE-4764 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 11.0.0.Beta3 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > > The customer asking why the web console is only available after all servers are registered in the Domain. > If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface. > In the log file, the HTTP management interface is enable in the end of the events: > ~~~ > [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting > [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1 > [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) > [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1 > [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999 > [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one > 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one' > [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two > [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one > 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two' > [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1 > [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand) > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4764) Availability of web console during the startup of the Domain Controller

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFCORE-4764?page=com.atlassian.jira.plug... ] Harald Pehl commented on WFCORE-4764: ------------------------------------- Hi [~yersan] sorry for the delay, I'll try to test your PR this week and give feedback asap. > Availability of web console during the startup of the Domain Controller > ----------------------------------------------------------------------- > > Key: WFCORE-4764 > URL: https://issues.redhat.com/browse/WFCORE-4764 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 11.0.0.Beta3 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > > The customer asking why the web console is only available after all servers are registered in the Domain. > If the customer starts a domain controller using the host.xml file for example and enables all servers to auto-start="true" the web console is not available until all servers are registered and the browser prompts to add a new interface. > In the log file, the HTTP management interface is enable in the end of the events: > ~~~ > [Host Controller] 18:41:29,247 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting > [Host Controller] 18:41:30,208 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,210 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:30,284 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1 > [Host Controller] 18:41:30,342 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,356 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) > [Host Controller] 18:41:30,383 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.4.Final-redhat-1 > [Host Controller] 18:41:30,478 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.5.Final-redhat-1 > [Host Controller] 18:41:30,603 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > [Host Controller] 18:41:30,647 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /opt/jboss-eap-7.1/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > [Host Controller] 18:41:30,705 INFO [org.jboss.as.remoting] (MSC service thread 1-8) WFLYRMT0001: Listening on 127.0.0.1:9999 > [Host Controller] 18:41:32,922 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:32,990 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,046 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,112 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [Host Controller] 18:41:33,612 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one > 18:41:33,665 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one' > [Host Controller] 18:41:35,496 INFO [org.jboss.as.host.controller] (management task-1) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 348b688d (inbound) of Remoting connection 0f97728d to localhost/127.0.0.1:53171 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:35,562 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-two > [Host Controller] 18:41:35,582 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) WFLYHC0020: Registering server server-one > 18:41:35,606 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-two' > [Host Controller] 18:41:38,901 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0021: Server [Server:server-two] connected using connection [Channel ID 114e3864 (inbound) of Remoting connection 30f65708 to localhost/127.0.0.1:42083 of endpoint "master:MANAGEMENT" <46167ef2>] > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://127.0.0.1:9990/management and https://127.0.0.1:-1/management > [Host Controller] 18:41:38,969 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0053: Admin console listening on http://127.0.0.1:9990 and https://127.0.0.1:-1 > [Host Controller] 18:41:38,970 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) (Host Controller) started in 10487ms - Started 77 of 79 services (23 services are lazy, passive or on-demand) > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFWIP-287: -------------------------------------- @Stefano Maestri @Jeff Mesnil hi guys, this should be addressed by separate RFE as discussed above with [~rhusar], wdyt? > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFWIP-287 at 1/21/20 6:10 AM: --------------------------------------------------------------- [~maeste] [~jmesnil]hi guys, this should be addressed by separate RFE as discussed above with [~rhusar], wdyt? was (Author: mnovak): @Stefano Maestri @Jeff Mesnil hi guys, this should be addressed by separate RFE as discussed above with [~rhusar], wdyt? > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak reopened WFWIP-287: ---------------------------------- > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak closed WFWIP-287. -------------------------------- Resolution: Rejected > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1053) Automate Weight < 100 https://github.com/kiali/kiali/pull/2108

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1053?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1053: ------------------------------------- Assignee: Hayk Hovsepyan > Automate Weight < 100 https://github.com/kiali/kiali/pull/2108 > -------------------------------------------------------------- > > Key: SWSQE-1053 > URL: https://issues.redhat.com/browse/SWSQE-1053 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1053) Automate Weight < 100 https://github.com/kiali/kiali/pull/2108

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1053?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1053: ---------------------------------- Sprint: Kiali Sprint #32 > Automate Weight < 100 https://github.com/kiali/kiali/pull/2108 > -------------------------------------------------------------- > > Key: SWSQE-1053 > URL: https://issues.redhat.com/browse/SWSQE-1053 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1047) Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1047?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1047. ----------------------------------- Resolution: Done Manual task is done, issue is opened: https://github.com/kiali/kiali/issues/2127 Automation is done. > Kiali Validations sync-up > ------------------------- > > Key: SWSQE-1047 > URL: https://issues.redhat.com/browse/SWSQE-1047 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Check all actual validations in https://kiali.io/documentation/validations/ > Sync up in Polarion testcases. > UI Automations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1048: ------------------------------------- Assignee: Hayk Hovsepyan (was: Sunil Kondkar) > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1048. ----------------------------------- Resolution: Done > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- Thanks [~skondkar]. All described issues are logged in https://github.com/kiali/kiali/issues/2127 > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Daniele Zonca commented on DROOLS-4950: --------------------------------------- [~jomarko] I think we should/could highlight better that expression and graphical editor are two completely different things: using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3447) Remove "DMN Asset" dependency from TitledAttachmentFileWidget

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-3447?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-3447: ------------------------------- Issue Type: Enhancement (was: Bug) > Remove "DMN Asset" dependency from TitledAttachmentFileWidget > ------------------------------------------------------------- > > Key: DROOLS-3447 > URL: https://issues.redhat.com/browse/DROOLS-3447 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > > Currently, TitledAttachmentFileWidget use ProjectAssetsQuery to retrieve the "dmn" files. > Implicitly, this means that *if* (for whatever reason) dmn editor is disabled, the dmn file are not retrieved. Wording differently, this creates an implicit dependency between scenariosimulation and dmn editor. > Fix it so that TitledAttachmentFileWidget could find dmn files regardless of dmn editor. > Look at left dock that shows all the files of the project. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12927) wildfly 8.2 huge memory allocation during and after deployement

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12927?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12927: ------------------------------------------- Is there a reason to use container that has been released almost 5 years ago? Anyway WFLY does not have product support, can you please check if WFLY 19 behaves in the same way? > wildfly 8.2 huge memory allocation during and after deployement > --------------------------------------------------------------- > > Key: WFLY-12927 > URL: https://issues.redhat.com/browse/WFLY-12927 > Project: WildFly > Issue Type: Bug > Reporter: sandev sandev > Assignee: Bartosz Baranowski > Priority: Major > Attachments: threads.png > > > I am using wildfly 8.2.1 final to deploy java ee 7 maven web application wars about 30 war with dependence between them using rmi remote ejb. I found that the server consumes a lot of memory special on startup of the server to 8 g my java opt are -xms 8g -xmx 8g -metaspacesize 1g .so I use java "visualvm" to understand what is happening. I found that the most consumed memory is for 2 types of threads at deploy: MSC service thread and after deploy finish: DeployementScanner-threads in additional that no user use the server or the deployed application this server was just for test > my question is why wildfly starts with about 3g and after some time the memory growth to ~= 8g without any action on the server its idle any help to solve this problem please -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12927) wildfly 8.2 huge memory allocation during and after deployement

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12927?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFLY-12927: ----------------------------------------- Assignee: Bartosz Baranowski (was: Brian Stansberry) > wildfly 8.2 huge memory allocation during and after deployement > --------------------------------------------------------------- > > Key: WFLY-12927 > URL: https://issues.redhat.com/browse/WFLY-12927 > Project: WildFly > Issue Type: Bug > Reporter: sandev sandev > Assignee: Bartosz Baranowski > Priority: Major > Attachments: threads.png > > > I am using wildfly 8.2.1 final to deploy java ee 7 maven web application wars about 30 war with dependence between them using rmi remote ejb. I found that the server consumes a lot of memory special on startup of the server to 8 g my java opt are -xms 8g -xmx 8g -metaspacesize 1g .so I use java "visualvm" to understand what is happening. I found that the most consumed memory is for 2 types of threads at deploy: MSC service thread and after deploy finish: DeployementScanner-threads in additional that no user use the server or the deployed application this server was just for test > my question is why wildfly starts with about 3g and after some time the memory growth to ~= 8g without any action on the server its idle any help to solve this problem please -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4957) Adapt ScenarioSimulation Wrapper for Kogito project

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4957?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4957: ------------------------------- Component/s: Scenario Simulation and Testing Labels: drools-tools (was: ) > Adapt ScenarioSimulation Wrapper for Kogito project > --------------------------------------------------- > > Key: DROOLS-4957 > URL: https://issues.redhat.com/browse/DROOLS-4957 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4958) Managing DMN FEEL type classes on KOGITO

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4958: ---------------------------------- Summary: Managing DMN FEEL type classes on KOGITO Key: DROOLS-4958 URL: https://issues.redhat.com/browse/DROOLS-4958 Project: Drools Issue Type: Sub-task Components: Scenario Simulation and Testing Reporter: Yeser Amer Assignee: Yeser Amer -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4957) Adapt ScenarioSimulation Wrapper for Kogito project

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4957: ---------------------------------- Summary: Adapt ScenarioSimulation Wrapper for Kogito project Key: DROOLS-4957 URL: https://issues.redhat.com/browse/DROOLS-4957 Project: Drools Issue Type: Sub-task Reporter: Yeser Amer Assignee: Yeser Amer -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4216?page=com.atlassian.jira.plug... ] Yeser Amer reassigned DROOLS-4216: ---------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Create runtime and testing version of kogito webapp > --------------------------------------------------- > > Key: DROOLS-4216 > URL: https://issues.redhat.com/browse/DROOLS-4216 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > > For each asset there should be two *kogito* webapp: > # a **development/testing** one, that should provide **VS CODE** features, > # a **runtime** one, without the above, to be used inside **VS CODE** > To allow *inheritance* and avoid code-duplication, a common, parent *jar* will also be implemented -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4216?page=com.atlassian.jira.plug... ] Yeser Amer reopened DROOLS-4216: -------------------------------- > Create runtime and testing version of kogito webapp > --------------------------------------------------- > > Key: DROOLS-4216 > URL: https://issues.redhat.com/browse/DROOLS-4216 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > For each asset there should be two *kogito* webapp: > # a **development/testing** one, that should provide **VS CODE** features, > # a **runtime** one, without the above, to be used inside **VS CODE** > To allow *inheritance* and avoid code-duplication, a common, parent *jar* will also be implemented -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4249) Implement client-side marshalling

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4249?page=com.atlassian.jira.plug... ] Yeser Amer reopened DROOLS-4249: -------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Implement client-side marshalling > --------------------------------- > > Key: DROOLS-4249 > URL: https://issues.redhat.com/browse/DROOLS-4249 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > > Implement a protoype for client-side marshalling -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4950: ------------------------------------- I think it is crucial to explain this difference directly in the popup, somewhere close to radio buttons create/define. > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4950: ------------------------------------ [~jomarko] I asked to [~danielezonca] ragarding this behavior, and I confirm you this is the expected one, because, in case of Graphical editor, EXPECTED collections works like a "contains" and not like an "equals". For example, If you try to put ?=[4] in the first row you will receive an error. In the case of an expression defined collection, it works like an "equals". I agree this is not clear and maybe it should be documented in some way (I didn't know it too). > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4920) Scenario simulation for DMN with collections throws en error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4920?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4920: ------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Scenario simulation for DMN with collections throws en error > ------------------------------------------------------------ > > Key: DROOLS-4920 > URL: https://issues.redhat.com/browse/DROOLS-4920 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-08 14-14-05.png, urgent.dmn > > > If a user tries to create a test scenario for [^urgent.dmn] he will get a [1] even when he is creating test scenario for the first time. > [1] > !Screenshot from 2020-01-08 14-14-05.png|thumbnail! > h3. Acceptance criteria > https://github.com/jboss-integration/bxms-qe-tests/pull/3048 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12999) EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/WFLY-12999?page=com.atlassian.jira.plugi... ] Ricardo Martin Camarero commented on WFLY-12999: ------------------------------------------------ This JIRA is for completing tests for WFCORE issue WFCORE-4803. > EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12999 > URL: https://issues.redhat.com/browse/WFLY-12999 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 19.0.0.Beta1 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > > Modify the test SaslLegacyMechanismConfigurationTestCase to include a test that configures {{DIGEST-MD5}} in the {{SASL_MECHANISMS}} option. > Test for core issue: https://issues.redhat.com/browse/WFCORE-4803 > Although a test in WFCORE was included it's better if this configuration is also tested in the real remoting/EJB scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12999) EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created WFLY-12999: ---------------------------------------------- Summary: EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security - test Key: WFLY-12999 URL: https://issues.redhat.com/browse/WFLY-12999 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 19.0.0.Beta1 Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero Modify the test SaslLegacyMechanismConfigurationTestCase to include a test that configures {{DIGEST-MD5}} in the {{SASL_MECHANISMS}} option. Test for core issue: https://issues.redhat.com/browse/WFCORE-4803 Although a test in WFCORE was included it's better if this configuration is also tested in the real remoting/EJB scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4953) Make Drools and Kogito compatible with Java 12

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4953?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4953: -------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) (was: 2020 Week 04-06 (from Jan 20)) > Make Drools and Kogito compatible with Java 12 > ---------------------------------------------- > > Key: DROOLS-4953 > URL: https://issues.redhat.com/browse/DROOLS-4953 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1046) Automate Validation links https://github.com/kiali/kiali/issues/2014

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1046?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1046. ----------------------------------- Resolution: Done > Automate Validation links https://github.com/kiali/kiali/issues/2014 > -------------------------------------------------------------------- > > Key: SWSQE-1046 > URL: https://issues.redhat.com/browse/SWSQE-1046 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4699) Supporting long value input

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4699?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4699: ------------------------------- Sprint: 2019 Week 44-46 (from Okt 28) (was: 2019 Week 44-46 (from Okt 28), 2020 Week 04-06 (from Jan 20)) > Supporting long value input > --------------------------- > > Key: DROOLS-4699 > URL: https://issues.redhat.com/browse/DROOLS-4699 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Description here: > https://issues.jboss.org/browse/DROOLS-4574?focusedCommentId=13794570&pag... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml and jboss-permissions.xml

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-2147?page=com.atlassian.jira.plug... ] Yeray Borges commented on WFCORE-2147: -------------------------------------- Glad to hear you were able to do the backport. This feature was completely merged and will be included in WF19. You are using WildFly 12, it is probably advisable to update to a more recent release and then keep up to date on the releases. > Impossible to use environment variables or system properties in permissions.xml and jboss-permissions.xml > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2147 > URL: https://issues.redhat.com/browse/WFCORE-2147 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Adrian Boangiu > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta7 > > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > {noformat} > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > {noformat} > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-4924: ------------------------------------------- Note: "without bind variable" may not be the only condition. I confirmed a materialized lambda with some complex RHS without bind variable. > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFLY-12980: ----------------------------------------- Assignee: Bartosz Baranowski > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Bartosz Baranowski > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Bartosz Baranowski resolved WFLY-12980. --------------------------------------- Resolution: Explained > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Bartosz Baranowski > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4924: -------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4924: -------------------------------------- Sprint: (was: 2020 Week 04-06 (from Jan 20)) > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4956) Normarize rule constraints for property reactivity and indexing

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-4956: ----------------------------------------- Summary: Normarize rule constraints for property reactivity and indexing Key: DROOLS-4956 URL: https://issues.redhat.com/browse/DROOLS-4956 Project: Drools Issue Type: Bug Components: core engine, executable model Affects Versions: 7.31.0.Final Reporter: Toshiya Kobayashi Assignee: Mario Fusco Having a constraint like {code:java} Person( name == "Toshiya" ) {code} is not really the same thing as {code:java} Person( "Toshiya" == name ) {code} In the second case not only you don't have property reactivity, but also you don't have indexing. This an inconsistent behaviour and hoping to fix it with a "normalization" phase where the second constraint got rewritten like the first before being analyzed by property reactivity and indexing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4956) Normarize rule constraints for property reactivity and indexing

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4956?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-4956: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Mario Fusco) > Normarize rule constraints for property reactivity and indexing > --------------------------------------------------------------- > > Key: DROOLS-4956 > URL: https://issues.redhat.com/browse/DROOLS-4956 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.31.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Having a constraint like > {code:java} > Person( name == "Toshiya" ) > {code} > is not really the same thing as > {code:java} > Person( "Toshiya" == name ) > {code} > In the second case not only you don't have property reactivity, but also you don't have indexing. This an inconsistent behaviour and hoping to fix it with a "normalization" phase where the second constraint got rewritten like the first before being analyzed by property reactivity and indexing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4805) WildFly Security Manager does not act for javaagents

by Boris Unckel (Jira)

Boris Unckel created WFCORE-4805: ------------------------------------ Summary: WildFly Security Manager does not act for javaagents Key: WFCORE-4805 URL: https://issues.redhat.com/browse/WFCORE-4805 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Boris Unckel Assignee: Darran Lofthouse The WildFly Core Security Manager cares for modules and deployed artifacts. It offers a JavaEE 7 compliant solution to permissions.xml in META-INF of EARs/WARs. Unfortunately it does not take care of javaagents, specified in https://docs.oracle.com/javase/8/docs/api/java/lang/instrument/package-su... OpenSource: https://inspectit.github.io/inspectit-ocelot/docs/getting-started/quick-s... java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "setContextClassLoader")" in code source "(file:/opt/inspectit/inspectit-ocelot-agent-0.6.jar <no signer certificates>)" of "sun.misc.Launcher$AppClassLoader@18b4aac2") at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295) at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192) at java.lang.Thread.setContextClassLoader(Thread.java:1474) at rocks.inspectit.ocelot.bootstrap.AgentManager.startOrReplaceInspectitCore(AgentManager.java:49) at rocks.inspectit.ocelot.agent.AgentMain.startAgent(AgentMain.java:78) at rocks.inspectit.ocelot.agent.AgentMain.lambda$premain$0(AgentMain.java:67) at java.lang.Thread.run(Thread.java:748) The specified JARs need AllPermission Config in the same way as container modules. Other Examples for JavaAgents - closed source: https://docs.appdynamics.com/display/PRO45/Java+Agent https://docs.appdynamics.com/display/PRO45/JBoss+and+Wildfly+Startup+Sett... https://docs.appdynamics.com/display/PRO45/Java+Security+Manager+Configur... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4802) Upgrade httpcomponents httpclient to 4.5.11 and httpcore to 4.4.13

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4802?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4802: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4059 (was: https://issues.redhat.com/browse/WFCORE-4802) > Upgrade httpcomponents httpclient to 4.5.11 and httpcore to 4.4.13 > ------------------------------------------------------------------ > > Key: WFCORE-4802 > URL: https://issues.redhat.com/browse/WFCORE-4802 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 11.0.0.Beta8 > > > I have set the component to management as other than use within testsuites these components are used within the git integration for server configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml and jboss-permissions.xml

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFCORE-2147?page=com.atlassian.jira.plug... ] Boris Unckel commented on WFCORE-2147: -------------------------------------- Hello [~yersan] thanks a lot for your howto. I have backported it successfully to WildFly Core 4 / WildFly 12, it works. > Impossible to use environment variables or system properties in permissions.xml and jboss-permissions.xml > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2147 > URL: https://issues.redhat.com/browse/WFCORE-2147 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Adrian Boangiu > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta7 > > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > {noformat} > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > {noformat} > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4955) [DMN Designer] Blog post - DMN Elements suggestions for FEEL code completion

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4955: --------------------------------------- Summary: [DMN Designer] Blog post - DMN Elements suggestions for FEEL code completion Key: DROOLS-4955 URL: https://issues.redhat.com/browse/DROOLS-4955 Project: Drools Issue Type: Task Reporter: Guilherme Gomes Assignee: Guilherme Gomes -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4955) [DMN Designer] Blog post - DMN Elements suggestions for FEEL code completion

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4955?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4955: ------------------------------------ Description: Create a blog post for https://issues.redhat.com/browse/BAPL-1480 > [DMN Designer] Blog post - DMN Elements suggestions for FEEL code completion > ---------------------------------------------------------------------------- > > Key: DROOLS-4955 > URL: https://issues.redhat.com/browse/DROOLS-4955 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > > Create a blog post for https://issues.redhat.com/browse/BAPL-1480 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1046) Automate Validation links https://github.com/kiali/kiali/issues/2014

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1046?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1046: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/241 > Automate Validation links https://github.com/kiali/kiali/issues/2014 > -------------------------------------------------------------------- > > Key: SWSQE-1046 > URL: https://issues.redhat.com/browse/SWSQE-1046 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4804) Topology gets loading when the write lock has been acquired on a DC

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4804?page=com.atlassian.jira.plug... ] Yeray Borges moved HAL-1643 to WFCORE-4804: ------------------------------------------- Project: WildFly Core (was: HAL) Key: WFCORE-4804 (was: HAL-1643) Workflow: GIT Pull Request workflow (was: GIT Pull Request workflow with automatic PR triggers) Component/s: Management (was: Domain Management) Affects Version/s: 11.0.0.Beta7 (was: 3.2.1.Final) > Topology gets loading when the write lock has been acquired on a DC > ------------------------------------------------------------------- > > Key: WFCORE-4804 > URL: https://issues.redhat.com/browse/WFCORE-4804 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 11.0.0.Beta7 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > > Topology information is loaded by using Composite operations. A composite operation could require the write lock on the DC when there is more than one slave in the domain. In this scenario, the DC's write lock is acquired until the overall operation, which is being executed in DC and in all the slaves, finishes. > If there is another operation being executed in the DC that previously has acquired the write lock, e.g servers in the domain are being started or an application is being deployed, the topology won't be able to load. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4803) EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/WFCORE-4803?page=com.atlassian.jira.plug... ] Ricardo Martin Camarero moved JBEAP-18530 to WFCORE-4803: --------------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4803 (was: JBEAP-18530) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: EJB) (was: Security) Affects Version/s: 11.0.0.Beta7 (was: 7.2.5.GA) QE Test Coverage: (was: +) Fix Version/s: (was: 7.2.8.GA) > EJB Client authentication does not work using SASL DIGEST-MD5 and EXTERNAL mechanisms in Legacy security > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4803 > URL: https://issues.redhat.com/browse/WFCORE-4803 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Beta7 > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > > The application does not working when use the DIGEST-MD5 mechanism in the legacy security. This this the configuration on standalone.xml: > {code:java} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <http-connector name="http-remoting-connector" connector-ref="https" security-realm="ApplicationRealm"> > <sasl> > <include-mechanisms value="DIGEST-MD5"/> > <qop value="auth"/> > <strength value="medium"/> > <server-auth value="false"/> > <reuse-session value="false"/> > <policy> > <forward-secrecy value="true"/> > <no-active value="false"/> > <no-anonymous value="false"/> > <no-dictionary value="true"/> > <no-plain-text value="false"/> > <pass-credentials value="true"/> > </policy> > </sasl> > </http-connector> > </subsystem> > {code} > Using this configuration I have seen this exception in the application: > {code:java} > 019-12-16 09:08:44,132 TRACE [org.wildfly.security] (default task-1) Handling RealmCallback: selected = [RemotingRealm] > 2019-12-16 09:08:44,132 TRACE [org.wildfly.security] (default task-1) Handling NameCallback: authenticationName = stubejbclient > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Principal assigning: [stubejbclient], pre-realm rewritten: [stubejbclient@RemotingRealm], realm name: [DIGEST-MD5], post-realm rewritten: [stubejbclient@RemotingRealm], realm rewritten: [stubejbclient@RemotingRealm] > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling CredentialCallback: failed to obtain credential > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling RealmCallback: selected = [RemotingRealm] > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling NameCallback: authenticationName = stubejbclient > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling CredentialCallback: failed to obtain credential > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling RealmCallback: selected = [RemotingRealm] > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling NameCallback: authenticationName = stubejbclient > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling PasswordCallback: PasswordCredential may not be supported > 2019-12-16 09:08:44,133 TRACE [org.jboss.remoting.remote.server] (default task-1) Server sending authentication rejected: javax.security.sasl.SaslException: ELY05051: Callback handler does not support credential acquisition [Caused by org.wildfly.security.auth.callback.FastUnsupportedCallbackException: javax.security.auth.callback.PasswordCallback@1cf94092] > at org.wildfly.security.mechanism.digest.PasswordDigestObtainer.getSaltedPasswordFromPasswordCallback(PasswordDigestObtainer.java:295) > at org.wildfly.security.mechanism.digest.PasswordDigestObtainer.handleUserRealmPasswordCallbacks(PasswordDigestObtainer.java:112) > at org.wildfly.security.sasl.digest.AbstractDigestMechanism.handleUserRealmPasswordCallbacks(AbstractDigestMechanism.java:195) > at org.wildfly.security.sasl.digest.DigestSaslServer.validateDigestResponse(DigestSaslServer.java:264) > at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateMessage(DigestSaslServer.java:363) > at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:199) > at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateResponse(DigestSaslServer.java:336) > at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58) > at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106) > at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:59) > at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245) > at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217) > at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.wildfly.security.auth.callback.FastUnsupportedCallbackException: javax.security.auth.callback.PasswordCallback@1cf94092 > 2019-12-16 09:08:44,133 TRACE [org.wildfly.security] (default task-1) Handling AuthenticationCompleteCallback: fail > 2019-12-16 09:08:44,133 TRACE [org.jboss.remoting.remote.server] (default task-1) No more authentication attempts allowed, closing the connection > {code} > It works to EAP 7.0.x but is not working to EAP 7.2.x. > The same configuration works on JBoss EAP 7.0.z. I'm attaching the EJB client, EJB service and standalone.xm. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-12980: ----------------------------------------- This should be rejected. Subsystems that require deployment unit processors require a reload. Users should evaluate their configuration in a non-production environment. If there is a high likelihood users would not notice this subsystem in their config and then feel an urgent need to remove it in production, i.e. not as part of a normal maintenance cycle that would bounce their deployments, then we should look into why they would feel that need and either fix whatever that problem is, or if it's inherent in the subsystem, reevaluate having it in the standard configuration. But I'm not aware of any problems like that. Is anyone else? > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4936) Unsaved changes dialog appears even if it just have been saved

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4936?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4936: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Unsaved changes dialog appears even if it just have been saved > -------------------------------------------------------------- > > Key: DROOLS-4936 > URL: https://issues.redhat.com/browse/DROOLS-4936 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Open a GRE file. Add a fact pattern. Save. > Close and the editor still thinks it has not been saved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4895) Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4895?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4895: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String ); > ---------------------------------------------------------------------------------- > > Key: DROOLS-4895 > URL: https://issues.redhat.com/browse/DROOLS-4895 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito > also {{RuleUnitDescriptionLoader}} may use this method in case {{createRuleUnitDescription( KiePackage pkg, Class<?> ruleUnit );} fails. However, this cannot happen in Drools 7, as the RuleUnit is always described by a Class, so it will always return null (it's a no-op after all). Reasons for backport are only code alignment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4742) [DMN Designer] Code Completion - Add suggestions about "requirements" and/or "dependencies" of a decision node

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4742?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4742: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Code Completion - Add suggestions about "requirements" and/or "dependencies" of a decision node > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4742 > URL: https://issues.redhat.com/browse/DROOLS-4742 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Add suggestions about "requirements" and/or "dependencies" of a decision node. > For instance, when a *Decision* {{routing}} has *Input Data* {{Customer}} in the information requirement, the code completion must show the suggestion {{Customer}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3936) [DMN Designer] Data Types - Constraints enumeration - skip zero values

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3936?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3936: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Data Types - Constraints enumeration - skip zero values > ---------------------------------------------------------------------- > > Key: DROOLS-3936 > URL: https://issues.redhat.com/browse/DROOLS-3936 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3936.png > > > In the Data Types tab > Data Types list > Constraints > Enumeration (for *days and time duration*): > !DROOLS-3936.png|thumbnail! > We must skip zeros, and show: > *1 day* > ...instead of showing: > *1 day, 0 hours, 0 minutes, 0 seconds* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3879?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3879: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Create Kogito version of Test Scenarios designer > ------------------------------------------------ > > Key: DROOLS-3879 > URL: https://issues.redhat.com/browse/DROOLS-3879 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor. > From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`. > Access to it has been "hided" behind a wrapper interface with three actual implementations: > * `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment > * `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment > * `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode). > As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place. > Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach. > Kogito-testing module is a standalone showcase that provides some minimum interaction to: > * load DMN files > * create DMN-related scesim assets, selecting one of the imported DMN. > Currently - RULE/data object model scesim is disabled. > Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset. > Some minimal tests may be done in the following way: > # full compilation (i.e. included GWT compilation) of the runtime module > # open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome > # inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will show the "New Scesim" popup, where user may choose to create a DMN or RULE scesim; of course, inside Chrome it is not possible to have a reference to other resources, so only "Rule" will work; at the same time, no Data model is available inside Chrome, so the right panel will be empty and the only expected result is an empty grid. > # edit the asset > # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().getContent() and store the returned xml > # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent method with the stored xml > Some tricks: to avoid CORS and other policy-related issues: > # set chrome://flags/#allow-insecure-localhost for invalid certificates error > # start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file. > /----/ > The "run scenario" functionality won't be implemented by this PR. > All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4507) Ability to externally execute project defined tests.

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4507?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4507: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Ability to externally execute project defined tests. > ---------------------------------------------------- > > Key: DROOLS-4507 > URL: https://issues.redhat.com/browse/DROOLS-4507 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Paul Brown > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Provide the ability to externally invoke project define tests scenario i.e via a rest api. > This is required in order for project defined tests to be reused and executed as part of a delivery pipeline and not from within business central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL and Background

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4636?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4636: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Update Scenario Cheatsheet to mention MVEL and Background > --------------------------------------------------------- > > Key: DROOLS-4636 > URL: https://issues.redhat.com/browse/DROOLS-4636 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.27.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Minor > Labels: CustomerFocus, drools-tools > > Update Scenario Cheatsheet for MVEL expression usage. > h3. Here are some topics that could be mentioned: > Expressions for Rule based scenarios for simple types > * Starts from "*#*" > * Runs for +properties+ > * Runs for +duplicated+ properties > * Returns the +same+ type as property type in *GIVEN* > * Returns boolean in *EXPECTED* > * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*" > * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean* > * Could run any of java function for the project > * Exports and imports as any other value > Limitations > 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+ > Use case: > User inputs 1/2 to Integer property > 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+ > Use case: > User inputs inexistent MVEL function in one of the properties > 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons > Use case: > User got one of the GIVEN fact expression excepted > 4.Mvel +cannot be mixed+ with simple expressions in one cell > Use case: > For cell inputs : > {code:java} > [#4+4,68] > #actualvalue>1 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4878) Test Scenario: fix support for default stateless kieSession

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4878?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4878: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Test Scenario: fix support for default stateless kieSession > ----------------------------------------------------------- > > Key: DROOLS-4878 > URL: https://issues.redhat.com/browse/DROOLS-4878 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > How to reproduce: > - edit kmodule.xml and create only a default stateless session > {code:java} > <kmodule xmlns="http://www.drools.org/xsd/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <kbase name="myKieBase"> > <ksession name="mySession" type="stateless" default="true"/> > </kbase> > </kmodule> > {code} > - create a Rule test scenario and specify in Setting panel {{stateless}} > - run -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4883) Test Scenario: create kie-docs content for Test Scenario Kie-server support

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4883?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4883: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Test Scenario: create kie-docs content for Test Scenario Kie-server support > --------------------------------------------------------------------------- > > Key: DROOLS-4883 > URL: https://issues.redhat.com/browse/DROOLS-4883 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Document how to enable test-scenario capability in Kie-server and how to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4688) [DMN Designer] Basic Code Completion for DMN Literal Expressions (7.6)

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4688?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4688: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Basic Code Completion for DMN Literal Expressions (7.6) > ---------------------------------------------------------------------- > > Key: DROOLS-4688 > URL: https://issues.redhat.com/browse/DROOLS-4688 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Users must have a basic code completion for DMN Literal Expressions. > This task is a MVP, and don't have any backend logic. The code completion is powered by a simple autocompleted of FEEL functions and a simple code highlight. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4485) [DMN Designer] Data Types - Add visual indication for showing the current drag level

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4485?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4485: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Data Types - Add visual indication for showing the current drag level > ------------------------------------------------------------------------------------ > > Key: DROOLS-4485 > URL: https://issues.redhat.com/browse/DROOLS-4485 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: drag-level.webm, image-2019-08-27-12-40-51-854.png > > > Show a visual indication of the current drag level. See (the blue line): > !image-2019-08-27-12-40-51-854.png|width=500! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3002) Redo PMML scorecards rules to use executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3002?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3002: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Redo PMML scorecards rules to use executable model > -------------------------------------------------- > > Key: DROOLS-3002 > URL: https://issues.redhat.com/browse/DROOLS-3002 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.12.0.Final > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Major > Labels: PMMLRefactor, drools-core > > Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model. > # Make further usage of POJOs to replace any types declared within the rule file > # Change the rules generated so that the rules are Java, based on the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4092) Default to executable model in the kie-maven-plugin

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4092?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4092: ----------------------------------- Sprint: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Default to executable model in the kie-maven-plugin > --------------------------------------------------- > > Key: DROOLS-4092 > URL: https://issues.redhat.com/browse/DROOLS-4092 > Project: Drools > Issue Type: Enhancement > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4370) Rename WITHDRL to YES_WITHDRL

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4370?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4370: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Rename WITHDRL to YES_WITHDRL > ----------------------------- > > Key: DROOLS-4370 > URL: https://issues.redhat.com/browse/DROOLS-4370 > Project: Drools > Issue Type: Task > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4858) Avoid materialized nested lambdas of method called "execute"

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4858?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4858: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Avoid materialized nested lambdas of method called "execute" > ------------------------------------------------------------ > > Key: DROOLS-4858 > URL: https://issues.redhat.com/browse/DROOLS-4858 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Fix For: 7.3.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4868) HA-CEP test with Executable Model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4868?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4868: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > HA-CEP test with Executable Model > --------------------------------- > > Key: DROOLS-4868 > URL: https://issues.redhat.com/browse/DROOLS-4868 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > org.kie.hacep.PodAsLeaderSnapshotTest.processMessagesAsLeaderAndCreateSnapshotTest -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-2845: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Extend the existing verifier to support DMN tables > -------------------------------------------------- > > Key: DROOLS-2845 > URL: https://issues.redhat.com/browse/DROOLS-2845 > Project: Drools > Issue Type: Epic > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: UX, drools-tools, verifier > > h1. Goal > Reuse the V&V created for Guided Decision Tables on the DMN tables. > h1. Workload divided to steps > I propose the work goes in the following steps. After each step I should be able to merge into master. > Steps: > # Move Verifier core to kie-wb-common > # Move V&V reporting UI to kie-wb-common > # Make the web worker connector reusable for different V&V types > # -Make a servlet module for DMN that allows the download of the Web Worker.- > # Create an adapter for DMN tables > # Add support for ranges ( these are given in DMN so no need to use JSR303 ) > # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense > The workload has changed. Now the goal is to reuse the DRL V&V codes in the existing DMN Codes. This means most of the work done for this ticket has no effect and the goal is to adjust to existing DMN V&V reporting, not the other way around. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4792) [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4792?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4792: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation > ---------------------------------------------------------------------------------- > > Key: DROOLS-4792 > URL: https://issues.redhat.com/browse/DROOLS-4792 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce {{RenderingInformation}} just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4793) [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4793?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4793: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager > ------------------------------------------------------------------------------------- > > Key: DROOLS-4793 > URL: https://issues.redhat.com/browse/DROOLS-4793 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce {{RenderingInformation}} just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4698?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4698: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.redhat.com/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-08 14-14-05.png, Screenshot from 2020-01-08 14-20-30.png, Screenshot from 2020-01-08 14-36-33.png, Screenshot from 2020-01-08 14-36-52.png, test urgent.scesim, urgent.dmn > > > Support is about both drools/java collections and dmn collections. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by users

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4905?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4905: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Code Completion - Index all elements named by users > ------------------------------------------------------------------ > > Key: DROOLS-4905 > URL: https://issues.redhat.com/browse/DROOLS-4905 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12998) MicroProfile OpenAPI: validate generated OpenAPI document

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-12998?page=com.atlassian.jira.plugi... ] Fabio Burzigotti moved WFWIP-292 to WFLY-12998: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-12998 (was: WFWIP-292) Component/s: MP OpenAPI (was: MP OpenAPI) > MicroProfile OpenAPI: validate generated OpenAPI document > ----------------------------------------------------------- > > Key: WFLY-12998 > URL: https://issues.redhat.com/browse/WFLY-12998 > Project: WildFly > Issue Type: Enhancement > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > Currently no validation is provided for generated document and actually the spec is not requesting for vendors to do that [1] but it would definitely be a key improvement for customers and users in general to know that the generated document is checked and appropriate action is taken in case content is not valid (e.g.: log WARN messages etc.). > Online Swagger Editor [2] was used to verify that non valid content was generated. > Also it should be evaluated whether to mention this behavior in community or product docs. > [1] > https://download.eclipse.org/microprofile/microprofile-open-api-1.1.2/mic... > [2] > https://editor.swagger.io/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4950: ------------------------------------ [~jomarko] Now I understood, thank you, I was looking only the second row :) > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1921) [GSS][7.2.2] HTTP External Security Not Supported by Elytron

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELY-1921: --------------------------------------- Summary: [GSS][7.2.2] HTTP External Security Not Supported by Elytron Key: ELY-1921 URL: https://issues.redhat.com/browse/ELY-1921 Project: WildFly Elytron Issue Type: Requirement Affects Versions: 1.11.0.Final Reporter: Ashley Abdel-Sayed Assignee: Ashley Abdel-Sayed For legacy security, there's an EXTERNAL HTTP authentication mechanism (io.undertow.security.impl.ExternalAuthenticationMechanism) which performs no verification and simply uses the principal that was passed from the REMOTE_USER attribute by the AJP protocol. There is a "ClientLoginModule" in legacy security used as such: https://access.redhat.com/solutions/3465231. It is a requirement to add an equivalent of this EXTERNAL mechanism available in legacy and Elytron-SASL for Elytron-HTTP in order to migrate away from legacy security. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12997) Upgrade jboss-ejb-client from 4.0.28.Final to ...

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFLY-12997?page=com.atlassian.jira.plugi... ] Tomas Hofman moved JBEAP-18529 to WFLY-12997: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12997 (was: JBEAP-18529) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.1.GA) > Upgrade jboss-ejb-client from 4.0.28.Final to ... > ------------------------------------------------- > > Key: WFLY-12997 > URL: https://issues.redhat.com/browse/WFLY-12997 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Tomas Hofman > Assignee: Ilia Vassilev > Priority: Major > > https://github.com/wildfly/jboss-ejb-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12980: ------------------------------------------- [~jkasik] & [~dlofthouse] - given above can this one be rejected? I dont think there is anything we can do about this. Any change to classloading/processors etc require :reload (unless change are scoped to deployment, IIRC?) > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4950: ------------------------------------- Please compare EXPECTED column in first and second row [~yamer] > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4870) Materialize consequences using Drools

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4870?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4870: -------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Materialize consequences using Drools > ------------------------------------- > > Key: DROOLS-4870 > URL: https://issues.redhat.com/browse/DROOLS-4870 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > > Currently consequences using Drools are not materialized (extracted in a different lambda) because they are capturing, as they use the relative bitmask instance. > We should find a way to pass the bitmask instance to the consequence so that we can materialize them. > This means we should probably not change only the compiler, but also the interpreter of the DSL -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4922) LinkageError: attempted duplicate class definition for materialized Lambda during incremental compilation

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4922?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4922: -------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > LinkageError: attempted duplicate class definition for materialized Lambda during incremental compilation > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4922 > URL: https://issues.redhat.com/browse/DROOLS-4922 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > In case of incremental compilation, say, a rule is changed: > - A lambda consequence (or a lambda predicate) has the same expression > - But an "import" statement is added to the rule > It will results in > {noformat} > [ERROR] testIdenticalConsequenceButImportChange[PATTERN_DSL](org.drools.modelcompiler.IncrementalCompilationTest) Time elapsed: 3.135 s <<< ERROR! > java.lang.LinkageError: loader org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader @2b0dc227 (instance of org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader, child of 'app' jdk.internal.loader.ClassLoaders$AppClassLoader) attempted duplicate class definition for org.drools.test.LambdaConsequence6F5B5EC739B778AE0EE14FA22BAFE144. > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:877) > at org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader.defineClass(DynamicProjectClassLoader.java:97) > at org.drools.reflective.classloader.ProjectClassLoader.defineType(ProjectClassLoader.java:183) > at org.drools.reflective.classloader.ProjectClassLoader.defineClass(ProjectClassLoader.java:195) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.reinitModifiedClasses(KieContainerImpl.java:323) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:243) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:236) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.updateToVersion(KieContainerImpl.java:194) > at org.drools.modelcompiler.IncrementalCompilationTest.testIdenticalConsequenceButImportChange(IncrementalCompilationTest.java:257) > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4561) DMN introspect PMML for output types

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4561?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4561: -------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > DMN introspect PMML for output types > ------------------------------------ > > Key: DROOLS-4561 > URL: https://issues.redhat.com/browse/DROOLS-4561 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Toshiya Kobayashi > Priority: Critical > Labels: good-first-issue > > Currently PMML is introspected for input parameters names and types. > Also for output parameters names. > Currently the feature is missing PMML introspection for output parameters types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4600) Embedded Camel endpoints don't work with executable model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4600?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4600: -------------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Embedded Camel endpoints don't work with executable model > --------------------------------------------------------- > > Key: DROOLS-4600 > URL: https://issues.redhat.com/browse/DROOLS-4600 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.27.0.Final > Reporter: Tibor Zimanyi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > When having and embedded Camel endpoint it DRL, it doesn't work with executable model. Reproducer can be found here [1]. For the test to reproduce the issue, it is needed to use executable model project in the buildAll() call here [2]. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/5f95febee0c081310... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-camel/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4924: -------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4761) Move kie-remote and hacep module into drools repo

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4761?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-4761: --------------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Move kie-remote and hacep module into drools repo > ------------------------------------------------- > > Key: DROOLS-4761 > URL: https://issues.redhat.com/browse/DROOLS-4761 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4706) Create an HACEP module to move Kafka dep away from ha-core and ha-remote

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4706?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-4706: --------------------------------------- Summary: Create an HACEP module to move Kafka dep away from ha-core and ha-remote (was: Create an HACEP module to move Kafka dep away from Kie-remote) > Create an HACEP module to move Kafka dep away from ha-core and ha-remote > ------------------------------------------------------------------------ > > Key: DROOLS-4706 > URL: https://issues.redhat.com/browse/DROOLS-4706 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4857) Prepare Hacep and Kie-remote modules to pass SonarCloud checks

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4857?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-4857: --------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Prepare Hacep and Kie-remote modules to pass SonarCloud checks > -------------------------------------------------------------- > > Key: DROOLS-4857 > URL: https://issues.redhat.com/browse/DROOLS-4857 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4860) Increase Unit test in the HA-Core and HA-remote to pass SonarCloud Checks

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4860?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-4860: --------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Increase Unit test in the HA-Core and HA-remote to pass SonarCloud Checks > ------------------------------------------------------------------------- > > Key: DROOLS-4860 > URL: https://issues.redhat.com/browse/DROOLS-4860 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4706) Create an HACEP module to move Kafka dep away from Kie-remote

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4706?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-4706: --------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Create an HACEP module to move Kafka dep away from Kie-remote > ------------------------------------------------------------- > > Key: DROOLS-4706 > URL: https://issues.redhat.com/browse/DROOLS-4706 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4945) Deficient Rows warning shows when Decision Table references items in a list

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4945?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4945: -------------------------------- Affects Version/s: 7.32.0.Final > Deficient Rows warning shows when Decision Table references items in a list > --------------------------------------------------------------------------- > > Key: DROOLS-4945 > URL: https://issues.redhat.com/browse/DROOLS-4945 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Michael Yarbrough > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools > > When creating a Guided Decision Table where one of the columns references a ParentObject->List->ChildObject->Field. The validator gives a warning that all rows are deficient rows > !image-2020-01-08-10-03-52-210.png|thumbnail! > !image-2020-01-08-10-05-17-751.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4918) Update Springboot and Springframework to 2.2.2 and 5.2.2 as kieparent

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4918?page=com.atlassian.jira.plug... ] Massimiliano Dessi resolved DROOLS-4918. ---------------------------------------- Resolution: Done > Update Springboot and Springframework to 2.2.2 and 5.2.2 as kieparent > --------------------------------------------------------------------- > > Key: DROOLS-4918 > URL: https://issues.redhat.com/browse/DROOLS-4918 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > > The springboot module of hacep refuse to start with the error > 2020-01-09 15:30:27.085 ERROR 10 --- [ main] o.s.boot.SpringApplication : Application run failed > org.springframework.core.annotation.AnnotationConfigurationException: Attribute 'proxyBeanMethods' in annotation [org.springframework.boot.autoconfigure.SpringBootApplication] is declared as an @AliasFor nonexistent attribute 'proxyBeanMethods' in annotation [org.springframework.context.annotation.Configuration].; nested exception is java.lang.NoSuchMethodException: org.springframework.context.annotation.Configuration.proxyBeanMethods() > at org.springframework.core.annotation.AnnotationUtils$AliasDescriptor.<init>(AnnotationUtils.java:2180) > currently it use 2.1.1 and spring 5.1.3 the proxyBeanMethods was introduced in springboot 2.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4915) Upgrade Hibernate validator

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4915?page=com.atlassian.jira.plug... ] Massimiliano Dessi resolved DROOLS-4915. ---------------------------------------- Resolution: Done > Upgrade Hibernate validator > --------------------------- > > Key: DROOLS-4915 > URL: https://issues.redhat.com/browse/DROOLS-4915 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4950: ------------------------------------ [~jomarko] Hi, what I see in second row is: GIVEN: List populated with graphical editor containing 1, 2 ,3 integers. EXPECTED: ?=[2] RUN RESULT = RED Which is correct, you are comparing 2 differents lists. > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4938) Reenable testScanNow in KieControllerRuleCapabilitiesIntegrationTest

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4938?page=com.atlassian.jira.plug... ] Tibor Zimanyi updated DROOLS-4938: ---------------------------------- Story Points: 5 > Reenable testScanNow in KieControllerRuleCapabilitiesIntegrationTest > -------------------------------------------------------------------- > > Key: DROOLS-4938 > URL: https://issues.redhat.com/browse/DROOLS-4938 > Project: Drools > Issue Type: Enhancement > Components: executable model > Reporter: Luca Molteni > Assignee: Tibor Zimanyi > Priority: Major > > After having defaulted to the executable model this test is failing sometimes, even if we disabled the executable model in the kjar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4928) Activate Exec Model in kie-server-integ-tests-controller

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4928?page=com.atlassian.jira.plug... ] Tibor Zimanyi updated DROOLS-4928: ---------------------------------- Story Points: 3 > Activate Exec Model in kie-server-integ-tests-controller > -------------------------------------------------------- > > Key: DROOLS-4928 > URL: https://issues.redhat.com/browse/DROOLS-4928 > Project: Drools > Issue Type: Enhancement > Components: executable model > Reporter: Luca Molteni > Assignee: Tibor Zimanyi > Priority: Major > > The stateless-session-kjar kjar inside the module doesn't use the executable model > <properties> > <generateModel>NO</generateModel> > </properties> > as KieControllerRuleCapabilitiesIntegrationTest became flaky -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4928) Activate Exec Model in kie-server-integ-tests-controller

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4928?page=com.atlassian.jira.plug... ] Tibor Zimanyi updated DROOLS-4928: ---------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > Activate Exec Model in kie-server-integ-tests-controller > -------------------------------------------------------- > > Key: DROOLS-4928 > URL: https://issues.redhat.com/browse/DROOLS-4928 > Project: Drools > Issue Type: Enhancement > Components: executable model > Reporter: Luca Molteni > Assignee: Tibor Zimanyi > Priority: Major > > The stateless-session-kjar kjar inside the module doesn't use the executable model > <properties> > <generateModel>NO</generateModel> > </properties> > as KieControllerRuleCapabilitiesIntegrationTest became flaky -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4938) Reenable testScanNow in KieControllerRuleCapabilitiesIntegrationTest

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4938?page=com.atlassian.jira.plug... ] Tibor Zimanyi updated DROOLS-4938: ---------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Reenable testScanNow in KieControllerRuleCapabilitiesIntegrationTest > -------------------------------------------------------------------- > > Key: DROOLS-4938 > URL: https://issues.redhat.com/browse/DROOLS-4938 > Project: Drools > Issue Type: Enhancement > Components: executable model > Reporter: Luca Molteni > Assignee: Tibor Zimanyi > Priority: Major > > After having defaulted to the executable model this test is failing sometimes, even if we disabled the executable model in the kjar. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4928) Activate Exec Model in kie-server-integ-tests-controller

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4928?page=com.atlassian.jira.plug... ] Tibor Zimanyi updated DROOLS-4928: ---------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) (was: 2020 Week 07-09 (from Feb 10)) > Activate Exec Model in kie-server-integ-tests-controller > -------------------------------------------------------- > > Key: DROOLS-4928 > URL: https://issues.redhat.com/browse/DROOLS-4928 > Project: Drools > Issue Type: Enhancement > Components: executable model > Reporter: Luca Molteni > Assignee: Tibor Zimanyi > Priority: Major > > The stateless-session-kjar kjar inside the module doesn't use the executable model > <properties> > <generateModel>NO</generateModel> > </properties> > as KieControllerRuleCapabilitiesIntegrationTest became flaky -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1049) install-ocp to support OCP 4.4

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1049?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1049: --------------------------------- Sprint: Kiali Sprint #32 > install-ocp to support OCP 4.4 > ------------------------------ > > Key: SWSQE-1049 > URL: https://issues.redhat.com/browse/SWSQE-1049 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > OCP 4.4 clusters will need to be created. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12995) ISPN008027: SQL error while fetching stored entry

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12995?page=com.atlassian.jira.plugi... ] Paul Ferraro closed WFLY-12995. ------------------------------- Resolution: Explained This is normal. When an application is undeployed, any expiration tasks are interrupted. > ISPN008027: SQL error while fetching stored entry > ------------------------------------------------- > > Key: WFLY-12995 > URL: https://issues.redhat.com/browse/WFLY-12995 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta2 > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Major > Attachments: clustering.html, wlf_20200918-130906-wildfly-service-2-server.log > > > This error was spotted in EAP Clustering tests where a relational MySQL Database is used to store replicated session data; > The error does not affects the overall fail rate that remains under the desired threshold; > Nevertheless the error was never observed in former tests and is hence considered worth reporting; > The error happened on node 2 of the 4 nodes cluster, twice: > - immediately after node 1 was failed (via EAP shutdown) > - immediately after node 3 was failed and then restored > The error log is the following: > {noformat} > 2020-01-18 13:16:53,621 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|4] (3) [wildfly2, wildfly3, wildfly4] > 2020-01-18 13:16:53,622 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100001: Node wildfly1 left the cluster > 2020-01-18 13:16:53,623 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|4] (3) [wildfly2, wildfly3, wildfly4] > 2020-01-18 13:16:53,623 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100001: Node wildfly1 left the cluster > 2020-01-18 13:16:53,623 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|4] (3) [wildfly2, wildfly3, wildfly4] > 2020-01-18 13:16:53,623 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100001: Node wildfly1 left the cluster > 2020-01-18 13:16:53,630 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|4] (3) [wildfly2, wildfly3, wildfly4] > 2020-01-18 13:16:53,631 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100001: Node wildfly1 left the cluster > 2020-01-18 13:16:53,664 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t1) [Context=cbnc.ear.b.war] ISPN100007: After merge (or coordinator change), recovered members [wildfly2, wildfly3, wildfly4] with topology id 8 > 2020-01-18 13:16:53,664 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p18-t66) [Context=client-mappings] ISPN100007: After merge (or coordinator change), recovered members [wildfly2, wildfly3, wildfly4] with topology id 15 > 2020-01-18 13:16:53,665 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p18-t65) [Context=cbnc.ear/clusterbench-ejb.jar/infinispan] ISPN100007: After merge (or coordinator change), recovered members [wildfly2, wildfly3, wildfly4] with topology id 19 > 2020-01-18 13:16:53,675 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t1) [Context=cbnc.ear.b.war] ISPN100008: Updating cache members list [wildfly2, wildfly3, wildfly4], topology id 9 > 2020-01-18 13:16:53,676 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t1) [Context=default-server] ISPN100007: After merge (or coordinator change), recovered members [wildfly2, wildfly3, wildfly4] with topology id 15 > 2020-01-18 13:16:53,677 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t1) [Context=cbnc.ear.c.war] ISPN100007: After merge (or coordinator change), recovered members [wildfly2, wildfly3, wildfly4] with topology id 8 > 2020-01-18 13:16:53,679 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t1) [Context=cbnc.ear.c.war] ISPN100008: Updating cache members list [wildfly2, wildfly3, wildfly4], topology id 9 > 2020-01-18 13:16:53,682 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t61) [Context=cbnc.ear.a.war] ISPN100007: After merge (or coordinator change), recovered members [wildfly2, wildfly3, wildfly4] with topology id 8 > 2020-01-18 13:16:53,697 INFO [org.infinispan.CLUSTER] (stateTransferExecutor-thread--p20-t61) [Context=cbnc.ear.a.war] ISPN100008: Updating cache members list [wildfly2, wildfly3, wildfly4], topology id 9 > 2020-01-18 13:16:53,720 ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (InfinispanSessionManager - 1) ISPN008027: SQL error while fetching stored entry with key: SessionAccessMetaDataKey(wfKG6Glx3bmXTmdyaQAiORrGTQ5s5uRCwP-X5UrZ), lockingKey: 6wfKG6Glx3bmXTmdyaQAiORrGTQ5s5uRCwP-X5UrZ: java.sql.SQLException: IJ031013: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@2c2b4a37 > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.tryLock(BaseWrapperManagedConnection.java:405) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:165) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedStatement.lock(WrappedStatement.java:138) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedResultSet.lock(WrappedResultSet.java:6022) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedResultSet.next(WrappedResultSet.java:2679) > at org.infinispan.persistence.jdbc@9.4.17.Final//org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.load(JdbcStringBasedStore.java:354) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.spi.SegmentedAdvancedLoadWriteStore.load(SegmentedAdvancedLoadWriteStore.java:46) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.manager.PersistenceManagerImpl.loadFromAllStores(PersistenceManagerImpl.java:642) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.loadAndCheckExpiration(PersistenceUtil.java:139) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.lambda$loadAndComputeInDataContainer$0(PersistenceUtil.java:97) > at org.infinispan@9.4.17.Final//org.infinispan.container.impl.AbstractInternalDataContainer.lambda$compute$3(AbstractInternalDataContainer.java:231) > at java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908) > at org.infinispan@9.4.17.Final//org.infinispan.container.impl.AbstractInternalDataContainer.compute(AbstractInternalDataContainer.java:230) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.loadAndComputeInDataContainer(PersistenceUtil.java:119) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.loadAndStoreInDataContainer(PersistenceUtil.java:53) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.loadInContext(CacheLoaderInterceptor.java:333) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.loadIfNeeded(CacheLoaderInterceptor.java:328) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.visitDataCommand(CacheLoaderInterceptor.java:195) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.visitGetKeyValueCommand(CacheLoaderInterceptor.java:130) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextThenAccept(BaseAsyncInterceptor.java:98) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.EntryWrappingInterceptor.visitDataReadCommand(EntryWrappingInterceptor.java:204) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.EntryWrappingInterceptor.visitGetKeyValueCommand(EntryWrappingInterceptor.java:192) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.handleDefault(DDAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitGetKeyValueCommand(DDAsyncInterceptor.java:106) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.handleDefault(DDAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitGetKeyValueCommand(DDAsyncInterceptor.java:106) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitDataReadCommand(PessimisticLockingInterceptor.java:61) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitGetKeyValueCommand(AbstractLockingInterceptor.java:107) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.TxInterceptor.visitGetKeyValueCommand(TxInterceptor.java:318) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndHandle(BaseAsyncInterceptor.java:183) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.BaseStateTransferInterceptor.handleReadCommand(BaseStateTransferInterceptor.java:193) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.BaseStateTransferInterceptor.visitGetKeyValueCommand(BaseStateTransferInterceptor.java:168) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndExceptionally(BaseAsyncInterceptor.java:123) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.InvocationContextInterceptor.visitCommand(InvocationContextInterceptor.java:90) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:56) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.BatchingInterceptor.handleDefault(BatchingInterceptor.java:69) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitGetKeyValueCommand(DDAsyncInterceptor.java:106) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitCommand(DDAsyncInterceptor.java:50) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.AsyncInterceptorChainImpl.invoke(AsyncInterceptorChainImpl.java:248) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:527) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:520) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.AbstractDelegatingCache.get(AbstractDelegatingCache.java:438) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.EncoderCache.get(EncoderCache.java:660) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.AbstractDelegatingCache.get(AbstractDelegatingCache.java:438) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.getValue(InfinispanSessionMetaDataFactory.java:100) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.findValue(InfinispanSessionMetaDataFactory.java:88) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.findValue(InfinispanSessionMetaDataFactory.java:56) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler.schedule(SessionExpirationScheduler.java:61) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler.schedule(SessionExpirationScheduler.java:45) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionManagerFactory$ScheduleExpirationTask.run(InfinispanSessionManagerFactory.java:286) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at org.jboss.as.clustering.common@19.0.0.Beta2-SNAPSHOT//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49) > at org.jboss.as.clustering.common@19.0.0.Beta2-SNAPSHOT//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70) > at java.base/java.lang.Thread.run(Thread.java:834) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > 2020-01-18 13:16:53,723 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (InfinispanSessionManager - 1) ISPN000136: Error executing command GetKeyValueCommand on Cache 'cbnc.ear.a.war', writing keys []: org.infinispan.persistence.spi.PersistenceException: SQL error while fetching stored entry with key: SessionAccessMetaDataKey(wfKG6Glx3bmXTmdyaQAiORrGTQ5s5uRCwP-X5UrZ), lockingKey: 6wfKG6Glx3bmXTmdyaQAiORrGTQ5s5uRCwP-X5UrZ > at org.infinispan.persistence.jdbc@9.4.17.Final//org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.load(JdbcStringBasedStore.java:361) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.spi.SegmentedAdvancedLoadWriteStore.load(SegmentedAdvancedLoadWriteStore.java:46) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.manager.PersistenceManagerImpl.loadFromAllStores(PersistenceManagerImpl.java:642) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.loadAndCheckExpiration(PersistenceUtil.java:139) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.lambda$loadAndComputeInDataContainer$0(PersistenceUtil.java:97) > at org.infinispan@9.4.17.Final//org.infinispan.container.impl.AbstractInternalDataContainer.lambda$compute$3(AbstractInternalDataContainer.java:231) > at java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908) > at org.infinispan@9.4.17.Final//org.infinispan.container.impl.AbstractInternalDataContainer.compute(AbstractInternalDataContainer.java:230) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.loadAndComputeInDataContainer(PersistenceUtil.java:119) > at org.infinispan@9.4.17.Final//org.infinispan.persistence.internal.PersistenceUtil.loadAndStoreInDataContainer(PersistenceUtil.java:53) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.loadInContext(CacheLoaderInterceptor.java:333) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.loadIfNeeded(CacheLoaderInterceptor.java:328) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.visitDataCommand(CacheLoaderInterceptor.java:195) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.CacheLoaderInterceptor.visitGetKeyValueCommand(CacheLoaderInterceptor.java:130) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextThenAccept(BaseAsyncInterceptor.java:98) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.EntryWrappingInterceptor.visitDataReadCommand(EntryWrappingInterceptor.java:204) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.EntryWrappingInterceptor.visitGetKeyValueCommand(EntryWrappingInterceptor.java:192) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.handleDefault(DDAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitGetKeyValueCommand(DDAsyncInterceptor.java:106) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.handleDefault(DDAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitGetKeyValueCommand(DDAsyncInterceptor.java:106) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitDataReadCommand(PessimisticLockingInterceptor.java:61) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitGetKeyValueCommand(AbstractLockingInterceptor.java:107) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:54) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.TxInterceptor.visitGetKeyValueCommand(TxInterceptor.java:318) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndHandle(BaseAsyncInterceptor.java:183) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.BaseStateTransferInterceptor.handleReadCommand(BaseStateTransferInterceptor.java:193) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.BaseStateTransferInterceptor.visitGetKeyValueCommand(BaseStateTransferInterceptor.java:168) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndExceptionally(BaseAsyncInterceptor.java:123) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.InvocationContextInterceptor.visitCommand(InvocationContextInterceptor.java:90) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:56) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.BatchingInterceptor.handleDefault(BatchingInterceptor.java:69) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitGetKeyValueCommand(DDAsyncInterceptor.java:106) > at org.infinispan@9.4.17.Final//org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:39) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.DDAsyncInterceptor.visitCommand(DDAsyncInterceptor.java:50) > at org.infinispan@9.4.17.Final//org.infinispan.interceptors.impl.AsyncInterceptorChainImpl.invoke(AsyncInterceptorChainImpl.java:248) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:527) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:520) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.AbstractDelegatingCache.get(AbstractDelegatingCache.java:438) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.EncoderCache.get(EncoderCache.java:660) > at org.infinispan@9.4.17.Final//org.infinispan.cache.impl.AbstractDelegatingCache.get(AbstractDelegatingCache.java:438) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.getValue(InfinispanSessionMetaDataFactory.java:100) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.findValue(InfinispanSessionMetaDataFactory.java:88) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.findValue(InfinispanSessionMetaDataFactory.java:56) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler.schedule(SessionExpirationScheduler.java:61) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.SessionExpirationScheduler.schedule(SessionExpirationScheduler.java:45) > at org.wildfly.clustering.web.infinispan@19.0.0.Beta2-SNAPSHOT//org.wildfly.clustering.web.infinispan.session.InfinispanSessionManagerFactory$ScheduleExpirationTask.run(InfinispanSessionManagerFactory.java:286) > at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at org.jboss.as.clustering.common@19.0.0.Beta2-SNAPSHOT//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49) > at org.jboss.as.clustering.common@19.0.0.Beta2-SNAPSHOT//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70) > at java.base/java.lang.Thread.run(Thread.java:834) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: java.sql.SQLException: IJ031013: Interrupted attempting lock: org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@2c2b4a37 > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.tryLock(BaseWrapperManagedConnection.java:405) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:165) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedStatement.lock(WrappedStatement.java:138) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedResultSet.lock(WrappedResultSet.java:6022) > at org.jboss.ironjacamar.jdbcadapters@1.4.20.Final//org.jboss.jca.adapters.jdbc.WrappedResultSet.next(WrappedResultSet.java:2679) > at org.infinispan.persistence.jdbc@9.4.17.Final//org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.load(JdbcStringBasedStore.java:354) > ... 64 more > 2020-01-18 13:18:50,041 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|5] (4) [wildfly2, wildfly3, wildfly4, wildfly1] > 2020-01-18 13:18:50,043 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100000: Node wildfly1 joined the cluster > 2020-01-18 13:18:50,043 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|5] (4) [wildfly2, wildfly3, wildfly4, wildfly1] > 2020-01-18 13:18:50,043 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100000: Node wildfly1 joined the cluster > 2020-01-18 13:18:50,044 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|5] (4) [wildfly2, wildfly3, wildfly4, wildfly1] > 2020-01-18 13:18:50,045 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100000: Node wildfly1 joined the cluster > 2020-01-18 13:18:50,052 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN000094: Received new cluster view for channel ejb: [wildfly2|5] (4) [wildfly2, wildfly3, wildfly4, wildfly1] > 2020-01-18 13:18:50,053 INFO [org.infinispan.CLUSTER] (thread-19,ejb,wildfly2) ISPN100000: Node wildfly1 joined the cluster > {noformat} > Find attached the complete logs and a report of the test phases; > Link to complete test run: [eap-7.x-clustering-db-session-shutdown-repl-mysql-5.7#48|https://eap-qe-j...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1055) Update pipelines when we have the maistra 1.1 build

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1055?page=com.atlassian.jira.plugi... ] Filip Brychta commented on SWSQE-1055: -------------------------------------- Prepared https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/triggers/job/u... but maistra 1.1 is still missing. > Update pipelines when we have the maistra 1.1 build > --------------------------------------------------- > > Key: SWSQE-1055 > URL: https://issues.redhat.com/browse/SWSQE-1055 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to update PR jobs to use correct maistra version based on target branch. > We need to update upstream pipelines. > Maistra installation job to support 1.1. > Downstream pipelines > Also pick correct kiali version v1.12 branch vs. master vs. v1.0 branch -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1055) Update pipelines when we have the maistra 1.1 build

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1055: ------------------------------------ Summary: Update pipelines when we have the maistra 1.1 build Key: SWSQE-1055 URL: https://issues.redhat.com/browse/SWSQE-1055 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We need to update PR jobs to use correct maistra version based on target branch. We need to update upstream pipelines. Maistra installation job to support 1.1. Downstream pipelines Also pick correct kiali version v1.12 branch vs. master vs. v1.0 branch -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 January 2020