April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3724) stop-servers following by a reload operation could end up in a long period with an unmanageable domain

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3724?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-3724: ------------------------------------ Assignee: Yeray Borges (was: Brian Stansberry) > stop-servers following by a reload operation could end up in a long period with an unmanageable domain > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3724 > URL: https://issues.jboss.org/browse/WFCORE-3724 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 5.0.0.Alpha2 > Reporter: Yeray Borges > Assignee: Yeray Borges > > When {{:stop-servers}} operation is used with a timeout different than 0, a graceful stop is performed on each server. > If the user executes {{/host=master:reload}} in a DC, the reload operation waits for the servers until they are completely stopped. This could be an issue for a DC since the user is unable to execute any operation meanwhile the reload op is waiting for the previous stop. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-1058) nested accessors with Sets - "not contains" is not a valid operator for MVEL

by Rahul Vanimisetty (JIRA)

[ https://issues.jboss.org/browse/JBRULES-1058?page=com.atlassian.jira.plug... ] Rahul Vanimisetty commented on JBRULES-1058: -------------------------------------------- Hi Edson , I am looking for a faster turnaround for https://issues.jboss.org/browse/DROOLS-2438. Could you please assign this ticket to yourself and respond. Need your help on this one asap. Thanks in advance. > nested accessors with Sets - "not contains" is not a valid operator for MVEL > ---------------------------------------------------------------------------- > > Key: JBRULES-1058 > URL: https://issues.jboss.org/browse/JBRULES-1058 > Project: JBRULES > Issue Type: Bug > Components: drools-compiler > Affects Versions: 4.0.0.GA > Reporter: Mark McNally > Assignee: Edson Tirelli > Fix For: 4.0.1 > > > Following does not work: > rule StateMatch > when > $ca:CandidateAssociation(nurseDetails.stateLicensures excludes patientDetails.state ) > then > retract( $ca ); > end > > > public class CandidateAssociation { > private PatientDetails patientDetails; > private NurseDetails nurseDetails; > private int overlapHours; > > public CandidateAssociation( PatientDetails patientDetails, NurseDetails nurseDetails) { > super(); > this.patientDetails = patientDetails; > this.nurseDetails = nurseDetails; > overlapHours = participantDetails.getNumberOverlapHourCnt(nurseDetails); > } > [...] > } > > public class NurseDetails { > private Set stateLicensures = new HashSet(); > [...] > } > public class PatientDetails { > private String state; > [...] > } > Edson suggested that the problem is that "not contains" is not a valid operator for MVEL. > Also Noticed that the following workaround did not work: > rule State > dialect "mvel" > when > $ca:CandidateAssociation( eval ( ! nurseDetails.stateLicensures.contains( patientDetails.state ) ) ) > then > retract( $ca ); > end > > This produced this Exception: > org.drools.rule.InvalidRulePackage: Unable to determine the used declarations : [Rule name=State, agendaGroup=MAIN, salience=0, no-loop=false] > at org.drools.rule.Package.checkValidity(Package.java:408) > at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:288) > at [...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2438) Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule

by Rahul Vanimisetty (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2438?page=com.atlassian.jira.plugi... ] Rahul Vanimisetty updated DROOLS-2438: -------------------------------------- Issue Type: Bug (was: Enhancement) > Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2438 > URL: https://issues.jboss.org/browse/DROOLS-2438 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.6.0.Final > Reporter: Rahul Vanimisetty > Assignee: Mario Fusco > Priority: Blocker > Labels: task > > In a drool template, if i am loading rules from a database, then as per my understanding each row in the database table represents a rule. So a drool template will generate a drl file in the following way : > rule 1 > when > condition(first row of db) > action > rule 2 > condition(2cd row of db) > then > action > etc. > My requirement is to have a dynamic drl generated in the following way : > rule 1 > when > condition 1(1st row of db) > condition 2 (2cd row of db) > condition 3 (3rd row of db) > etc > then > action > end > Please suggest a way to do this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10158) upgrade yasson to 1.0.1

by Scott Marlow (JIRA)

Scott Marlow created WFLY-10158: ----------------------------------- Summary: upgrade yasson to 1.0.1 Key: WFLY-10158 URL: https://issues.jboss.org/browse/WFLY-10158 Project: WildFly Issue Type: Task Components: REST Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 13.0.0.Beta1 Upgrade to get fix for [https://github.com/eclipse-ee4j/yasson/issues/56], which will help our testing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10157) version of the modules defined in wildfly core cannot be overrided in wildfly full build

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10157?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10157: ----------------------------------------- This is an RFE and involves a big change in how the server is built. The WildFly build brings in the core feature pack as a whole, including its dependencies, it does not rebuild it. WFLY-9911 was not about changing that. It simply changed the location where the dependencies the full build directly controls are declared. > version of the modules defined in wildfly core cannot be overrided in wildfly full build > ---------------------------------------------------------------------------------------- > > Key: WFLY-10157 > URL: https://issues.jboss.org/browse/WFLY-10157 > Project: WildFly > Issue Type: Bug > Components: Build System > Environment: latest WildFly master (commit id: 0565fe6a47a121f5d25e4810572a2d6f277420bc) > latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219) > Reporter: Lin Gao > > I suppose it is a bug but not for sure. > After WFLY-9911 is resolved, I think we are able to override version of modules defined in wildfly-core at maven build time too. > Like: > {code:java} > mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT -Dversion.io.undertow=2.0.2.Final > {code} > should produce module: io.undertow.core:2.0.2.Final instead of io.undertow.core:2.0.3.Final which is defined in the wildfly-core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3680) WFLYJMX0037 occurs with RBAC enabled when disconnecting JConsole

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3680?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-3680: ---------------------------- Labels: downstream_dependency (was: ) > WFLYJMX0037 occurs with RBAC enabled when disconnecting JConsole > ---------------------------------------------------------------- > > Key: WFCORE-3680 > URL: https://issues.jboss.org/browse/WFCORE-3680 > Project: WildFly Core > Issue Type: Bug > Components: JMX, Remoting, Security > Reporter: Bartosz Baranowski > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10157) version of the modules defined in wildfly core cannot be overrided in wildfly full build

by Lin Gao (JIRA)

Lin Gao created WFLY-10157: ------------------------------ Summary: version of the modules defined in wildfly core cannot be overrided in wildfly full build Key: WFLY-10157 URL: https://issues.jboss.org/browse/WFLY-10157 Project: WildFly Issue Type: Bug Components: Build System Environment: latest WildFly master (commit id: 0565fe6a47a121f5d25e4810572a2d6f277420bc) latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219) Reporter: Lin Gao Assignee: Paul Gier I suppose it is a bug but not for sure. After WFLY-9911 is resolved, I think we are able to override version of modules defined in wildfly-core at maven build time too. Like: {code:java} mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT -Dversion.io.undertow=2.0.2.Final {code} should produce module: io.undertow.core:2.0.2.Final instead of io.undertow.core:2.0.3.Final which is defined in the wildfly-core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10157) version of the modules defined in wildfly core cannot be overrided in wildfly full build

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10157?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-10157: ------------------------------ Assignee: (was: Paul Gier) > version of the modules defined in wildfly core cannot be overrided in wildfly full build > ---------------------------------------------------------------------------------------- > > Key: WFLY-10157 > URL: https://issues.jboss.org/browse/WFLY-10157 > Project: WildFly > Issue Type: Bug > Components: Build System > Environment: latest WildFly master (commit id: 0565fe6a47a121f5d25e4810572a2d6f277420bc) > latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219) > Reporter: Lin Gao > > I suppose it is a bug but not for sure. > After WFLY-9911 is resolved, I think we are able to override version of modules defined in wildfly-core at maven build time too. > Like: > {code:java} > mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT -Dversion.io.undertow=2.0.2.Final > {code} > should produce module: io.undertow.core:2.0.2.Final instead of io.undertow.core:2.0.3.Final which is defined in the wildfly-core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 April 2018