September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4577) Rule containing expired event and additional constraint incorrectly fired

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4577?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4577. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/8c4a260f764c77282beb363ddaa1585... > Rule containing expired event and additional constraint incorrectly fired > ------------------------------------------------------------------------- > > Key: DROOLS-4577 > URL: https://issues.jboss.org/browse/DROOLS-4577 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.27.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > > Migrating a project from Drools 6.5.x to 7.x results in a rule getting fired incorrectly when the following is involved: > * expired event > * additional constraint -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-214) Can't install more than one JDBC driver

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-214?page=com.atlassian.jira.plugin.... ] Jean Francois Denise updated WFWIP-214: --------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-cekit-modules/pull/94 (was: https://github.com/wildfly/wildfly-cekit-modules/pull/92) > Can't install more than one JDBC driver > --------------------------------------- > > Key: WFWIP-214 > URL: https://issues.jboss.org/browse/WFWIP-214 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Yeray Borges > Priority: Critical > > With latest image {{docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP7-1216 digest: sha256:a65337b39f0b84f803bd3f8561c2ac937bab316a7de2df50e3afe72f90906020 size: 951}} it is not possible to install more than one JDBC driver within S2I process. There is a bug in /opt/jboss/container/wildfly/s2i/install-common/install-common.sh, the /opt/eap/bin/launch/drivers.cli is always overwritten. > It should be enough to fix this line https://github.com/wildfly/wildfly-cekit-modules/blob/master/jboss/contai... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-186 at 9/30/19 4:16 AM: ------------------------------------------------------------- [~jmesnil] - could you also document in [1] User does not have to declare access mode in {{PersistentVolumeClaim}} as it is hardcoded to {{ReadWriteOnce}} - best would be to operator does not permit other value then {{ReadWriteOnce}} or validate it on create or update. [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sto... was (Author: mchoma): [~jmesnil] could you also document in [1] User does not have to declare access mode in {{PersistentVolumeClaim}} as it is hardcoded to {{ReadWriteOnce}} [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sto... > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Martin Choma reopened WFWIP-186: -------------------------------- > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-186: ------------------------------- Priority: Critical (was: Blocker) > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12608) Integration tests for OCSP followup

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-12608?page=com.atlassian.jira.plugin... ] Jan Stourac reassigned WFLY-12608: ---------------------------------- Assignee: Jan Stourac (was: Darran Lofthouse) > Integration tests for OCSP followup > ----------------------------------- > > Key: WFLY-12608 > URL: https://issues.jboss.org/browse/WFLY-12608 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Major > > Followup integration tests for OCSP feature into WildFly testsuite to comply with the feature test-plan. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3064) POJO Unification

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3064?page=com.atlassian.jira.plugi... ] Edoardo Vacchi resolved DROOLS-3064. ------------------------------------ Resolution: Deferred > POJO Unification > ----------------- > > Key: DROOLS-3064 > URL: https://issues.jboss.org/browse/DROOLS-3064 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > implement a general algorithm for recursive unification of POJO structures -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12608) Integration tests for OCSP followup

by Jan Stourac (Jira)

Jan Stourac created WFLY-12608: ---------------------------------- Summary: Integration tests for OCSP followup Key: WFLY-12608 URL: https://issues.jboss.org/browse/WFLY-12608 Project: WildFly Issue Type: Bug Components: Security Reporter: Jan Stourac Assignee: Darran Lofthouse Followup integration tests for OCSP feature into WildFly testsuite to comply with the feature test-plan. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-213) Can't resolve artifact for module when executing CLI modification

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-213?page=com.atlassian.jira.plugin.... ] Jean Francois Denise resolved WFWIP-213. ---------------------------------------- Resolution: Done The settings.xml are now properly set before user execution hooks. > Can't resolve artifact for module when executing CLI modification > ----------------------------------------------------------------- > > Key: WFWIP-213 > URL: https://issues.jboss.org/browse/WFWIP-213 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Blocker > > Using image {{docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP7-1216}} when we workaround the issues WFWIP-208 & WFWIP-212 the CLI modification still won't process successfully because of the exception: > {code:java} > I0926 13:20:23.465008 1 sti.go:697] Exception in thread "main" org.jboss.modules.ModuleLoadException: Error loading module from /opt/eap/modules/system/layers/base/org/apache/xerces/main/module.xml > I0926 13:20:23.465037 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:339) > I0926 13:20:23.465047 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:295) > I0926 13:20:23.465052 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:256) > I0926 13:20:23.465060 1 sti.go:697] at org.jboss.modules.LocalModuleFinder.parseModuleXmlFile(LocalModuleFinder.java:250) > I0926 13:20:23.465067 1 sti.go:697] at org.jboss.modules.LocalModuleFinder.lambda$findModule$1(LocalModuleFinder.java:195) > I0926 13:20:23.465075 1 sti.go:697] at java.base/java.security.AccessController.doPrivileged(Native Method) > I0926 13:20:23.465082 1 sti.go:697] at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:195) > I0926 13:20:23.465089 1 sti.go:697] at org.jboss.modules.ModuleLoader.findModule0(ModuleLoader.java:696) > I0926 13:20:23.465096 1 sti.go:697] at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:689) > I0926 13:20:23.465103 1 sti.go:697] at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:499) > I0926 13:20:23.465110 1 sti.go:697] at org.jboss.modules.DelegatingModuleLoader.preloadModule(DelegatingModuleLoader.java:57) > I0926 13:20:23.465117 1 sti.go:697] at org.jboss.modules.Module.addPaths(Module.java:1252) > I0926 13:20:23.465125 1 sti.go:697] at org.jboss.modules.Module.link(Module.java:1622) > I0926 13:20:23.465132 1 sti.go:697] at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > I0926 13:20:23.465141 1 sti.go:697] at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:299) > I0926 13:20:23.465147 1 sti.go:697] at org.jboss.modules.Main.main(Main.java:437) > I0926 13:20:23.465153 1 sti.go:697] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.12.0.SP02' (position: END_TAG seen ...esources>\n <artifact name="xerces:xercesImpl:2.12.0.SP02"/>... @26:57) > I0926 13:20:23.465159 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:1063) > I0926 13:20:23.465177 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:950) > I0926 13:20:23.465206 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:710) > I0926 13:20:23.465211 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:471) > I0926 13:20:23.465217 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:337) > I0926 13:20:23.465224 1 sti.go:697] ... 15 more > {code} > Because jboss-modules will try to resolve artifact from ~/.m2/settings.xml and galleon integration replaces this file before this error, there must be something wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12601) Eliminate StabilityMonitor usages in clustering subsystem

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFLY-12601?page=com.atlassian.jira.plugin... ] Richard Opalka commented on WFLY-12601: --------------------------------------- CountDownLifecycle listener needs to remove listener once target event is achieved - see my review comment. Otherwise changes to ServiceLifecycle looks good to me [~pferraro] > Eliminate StabilityMonitor usages in clustering subsystem > --------------------------------------------------------- > > Key: WFLY-12601 > URL: https://issues.jboss.org/browse/WFLY-12601 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Richard Opalka > Assignee: Paul Ferraro > Priority: Major > Fix For: 19.0.0.Beta1 > > Attachments: ServiceSupplier.png > > > Clustering needs to eliminate usages of StabilityMonitor because SM is not reliable. > It is possible that SM will prematurely inform about achieved stability even if it is not true. > The reason is SM is not propagated up the dependencies chain and thus it may report > about achieved stability even in case dependencies chain didn't finish its processing yet > and 'real' stability wasn't achieved yet. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2019