October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4684) Parser and Canonical Model Compiler error on Conditional Named Consequence

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4684?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-4684: ----------------------------------- Assignee: Luca Molteni (was: Mario Fusco) > Parser and Canonical Model Compiler error on Conditional Named Consequence > -------------------------------------------------------------------------- > > Key: DROOLS-4684 > URL: https://issues.jboss.org/browse/DROOLS-4684 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.28.0.Final > Environment: macOS 10.14.6, OpenJDK 1.8.0_222 > Reporter: Duncan Doyle > Assignee: Luca Molteni > Priority: Major > > See reproducer here: https://github.com/DuncanDoyle/drools-conditional-named-consequence-issue > When you use a Conditional Named Consequence {code}if{code} definition directly after an {code}accumulate{code}, Drools gives the following error when parsing the DRL: > {code} > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.28.0.Final:build (default-build) on project drools-conditional-named-consequence-issue: Execution default-build of goal org.kie:kie-maven-plugin:7.28.0.Final:build failed: Unable to get KieModule, Errors Existed: Error Messages: > [ERROR] Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=19, column=0 > [ERROR] text=Unable to resolve ObjectType 'if'] > [ERROR] --- > [ERROR] Warning Messages: > [ERROR] --- > [ERROR] Info Messages: > [ERROR] > {code} > When you add a constraint between the {code}accumulate{code} and the {code}if{code} statement of the Conditional Named Consequence, it works fine. > Also when you try to generate the canonical model from a DRL that contains a Conditional Named Consequence, you get the following error: > {code} > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.28.0.Final:generateModel (default-generateModel) on project drools-conditional-named-consequence-issue: A type incompatibility occurred while executing org.kie:kie-maven-plugin:7.28.0.Final:generateModel: org.drools.compiler.lang.descr.NamedConsequenceDescr cannot be cast to org.drools.compiler.lang.descr.PatternDescr > {code} > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-184) Can't specify arbitrary Persistent Volume Claim Name

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-184?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-184. ------------------------------ I consider resolution by documentation sufficient for now. > Can't specify arbitrary Persistent Volume Claim Name > ---------------------------------------------------- > > Key: WFWIP-184 > URL: https://issues.jboss.org/browse/WFWIP-184 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > I cant create PVC with arbitrary name. It must be empty [3] or "<CR name>-volume" [2] > When I specify PVC name I get error like > {code} > create Pod simple-jaxrs-eap72-0 in StatefulSet simple-jaxrs-eap72 failed error: Pod "simple-jaxrs-eap72-0" is invalid: spec.containers[0].volumeMounts[0].name: Not found: "simple-jaxrs-eap72-volume" > {code} > Is there any reason to not permit arbitrary PVC name? > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... > [2] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... > [3] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3797) Logging Subsystem test failures on IBM jdk

by Romain Pelisse (Jira)

[ https://issues.jboss.org/browse/WFCORE-3797?page=com.atlassian.jira.plugi... ] Romain Pelisse updated WFCORE-3797: ----------------------------------- Labels: downstream_dependency (was: ) > Logging Subsystem test failures on IBM jdk > ------------------------------------------ > > Key: WFCORE-3797 > URL: https://issues.jboss.org/browse/WFCORE-3797 > Project: WildFly Core > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 5.0.0.Alpha1, 5.0.0.Alpha2, 5.0.0.Alpha3, 5.0.0.Alpha4 > Environment: {noformat} > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00) > Maven home: /usr/lib/maven > Java version: 1.8.0_161, vendor: IBM Corporation > Java home: /usr/lib/java/ibm-java-8.0-5.11/jre > {noformat} > Reporter: Petr Kremensky > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > Fix For: 6.0.0.Beta1 > > > WildFly: Logging Subsystem unit tests fails on IBM jdk with: > {noformat} > java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:168) > at org.jboss.as.subsystem.test.TestModelControllerService.preBoot(TestModelControllerService.java:158) > at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:264) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:419) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372) > at java.lang.Thread.run(Thread.java:811) > {noformat} > The test works fine with *4.0.0.Final*, starts failing in *5.0.0.Alpha1*. > This doens't look like a functional issue to me as I was able to workaround the issue by either running the test with the older surefire instance ( -Dversion.surefire.plugin=2.19 is the last working ) or by extending {{surefire.system.args}} in pom.xml with {{-Djava.util.logging.manager=org.jboss.logmanager.LogManager}}. The other however produces the following warnings upon test execution > {noformat} > ... > [WARNING] The system property java.util.logging.manager is configured twice! The property appears in <argLine/> and any of <systemPropertyVariables/>, <systemProperties/> or user property. > [INFO] > [INFO] ------------------------------------------------------- > [INFO] T E S T S > [INFO] ------------------------------------------------------- > [INFO] Running org.jboss.as.logging.HandlerLegacyOperationsTestCase > [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/pkremens/devel/wildfly-core/logging/target/surefire-reports/2018-05-03T13-49-32_779-jvmRun1.dumpstream > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-988) Update PSI docs with additional resources

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-988?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-988: -------------------------------- Sprint: Kiali Sprint #30 > Update PSI docs with additional resources > ----------------------------------------- > > Key: SWSQE-988 > URL: https://issues.jboss.org/browse/SWSQE-988 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > We got new resources in istio-dev, need to document that in https://mojo.redhat.com/docs/DOC-1191229 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-988) Update PSI docs with additional resources

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-988?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-988. --------------------------------- Resolution: Done > Update PSI docs with additional resources > ----------------------------------------- > > Key: SWSQE-988 > URL: https://issues.jboss.org/browse/SWSQE-988 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > We got new resources in istio-dev, need to document that in https://mojo.redhat.com/docs/DOC-1191229 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12718: ------------------------------------- [~tommaso-borgato] Can you past the output of: {code} /subsystem=distributable-web:read-resource(recursive=true) {code} > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12718: -------------------------------- Component/s: (was: Web (Undertow)) > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4707) Update HACEP docs for Update kjar

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4707: ------------------------------------------ Summary: Update HACEP docs for Update kjar Key: DROOLS-4707 URL: https://issues.jboss.org/browse/DROOLS-4707 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4708) Create an HACEP example with update kjar at runtime

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4708: ------------------------------------------ Summary: Create an HACEP example with update kjar at runtime Key: DROOLS-4708 URL: https://issues.jboss.org/browse/DROOLS-4708 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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)

Massimiliano Dessi created DROOLS-4706: ------------------------------------------ Summary: Create an HACEP module to move Kafka dep away from Kie-remote Key: DROOLS-4706 URL: https://issues.jboss.org/browse/DROOLS-4706 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 October 2019