May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1167) Comparison operation error

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1167?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2512 to DROOLS-1167: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1167 (was: GUVNOR-2512) Workflow: GIT Pull Request workflow (was: classic default workflow) Affects Version/s: 6.4.0.Final (was: drools_6.4.0.Final) > Comparison operation error > -------------------------- > > Key: DROOLS-1167 > URL: https://issues.jboss.org/browse/DROOLS-1167 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Environment: OracleLinux 6, Java 7/8 > Reporter: Pierangelo Repetti > Attachments: failing_rule.drl > > > I migrated a set of rules from version 5.4 to 6.3. All rules are "Technical rules". > After migration, I get the following error > _Unable to Analyse Expression value != 0: [Error: Comparison operation requires compatible types. Found class org.mvel2.util.MethodStub and class java.lang.Integer] [Near : {... value != 0 ....}] ^ [Line: 29, Column: 9] > _ > on the following line of a rule > _$imponibile : RuleElement(label=="IMPONIBILE", value != 0, imponibile : value, imponibile_artmap : artmap);_ > RuleElement is a model class (loaded as a dependency) and declares a value attribute like > _private Double value;_ > The same rule compiled without problems in 5.4. > Thanks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1535) Potential forever blocking for suspend() and resume() calls in ManagedServer

by Yeray Santana Borges (JIRA)

Yeray Santana Borges created WFCORE-1535: -------------------------------------------- Summary: Potential forever blocking for suspend() and resume() calls in ManagedServer Key: WFCORE-1535 URL: https://issues.jboss.org/browse/WFCORE-1535 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Yeray Santana Borges Assignee: Brian Stansberry Currently ManagedServer is using blocking calls for suspend() and resume() operantions. Those calls can potentially wait forever for a server response. This issue has been opened to change them allowing the use of a BlockingQueueOperationListener and prevent that potential situation. Basically it continues the changes already implemented in WFCORE-1473, but this time applying them for :suspend-servers (without an explicity timeout) and :resume-servers operations in a domain mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1535) Potential forever blocking for suspend() and resume() calls in ManagedServer

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1535?page=com.atlassian.jira.plugi... ] Yeray Santana Borges reassigned WFCORE-1535: -------------------------------------------- Assignee: Yeray Santana Borges (was: Brian Stansberry) > Potential forever blocking for suspend() and resume() calls in ManagedServer > ----------------------------------------------------------------------------- > > Key: WFCORE-1535 > URL: https://issues.jboss.org/browse/WFCORE-1535 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Yeray Santana Borges > Assignee: Yeray Santana Borges > > Currently ManagedServer is using blocking calls for suspend() and resume() operantions. Those calls can potentially wait forever for a server response. > This issue has been opened to change them allowing the use of a BlockingQueueOperationListener and prevent that potential situation. Basically it continues the changes already implemented in WFCORE-1473, but this time applying them for :suspend-servers (without an explicity timeout) and :resume-servers operations in a domain mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6083) Removing of non-existent login-module finishes with outcome success

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-6083?page=com.atlassian.jira.plugin.... ] Chao Wang resolved WFLY-6083. ----------------------------- Resolution: Duplicate Issue duplicates WFCORE-1523 > Removing of non-existent login-module finishes with outcome success > ------------------------------------------------------------------- > > Key: WFLY-6083 > URL: https://issues.jboss.org/browse/WFLY-6083 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Priority: Minor > > In case when non-existent login-module is removed through Management CLI, opertation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-362) fix jvm management model for server and groups

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-362?page=com.atlassian.jira.plugin... ] Ken Wills commented on WFCORE-362: ---------------------------------- WFCORE-1527 has been opened to address the missing parent on an ignoring slave, so resolving this one. > fix jvm management model for server and groups > ---------------------------------------------- > > Key: WFCORE-362 > URL: https://issues.jboss.org/browse/WFCORE-362 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Ken Wills > Labels: rhq > > We need to update the JVM child resource definition for server-groups and servers to only allow a single JVM configuration (i.e. configuration=JVM) resource. Currently only the first configured VM is used, where the name is the reference to the corresponding host level JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-771) Server resources off the host resource allow the removal of deployments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-771?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-771: ------------------------------------ Labels: 2.2 (was: ) > Server resources off the host resource allow the removal of deployments > ----------------------------------------------------------------------- > > Key: WFCORE-771 > URL: https://issues.jboss.org/browse/WFCORE-771 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Ken Wills > Priority: Critical > Labels: 2.2 > > The following command succeeds, but leaves the deployment in a state that it can't be undeployed. > {code} > /host=master/server=server-two/deployment=wildfly-helloworld.war:remove > {code} > My guess is that operation should fail or further operations to remove the deployment should succeed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6083) Removing of non-existent login-module finishes with outcome success

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6083?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6083: ---------------------------------------- [~soul2zimate] I don't mind at all; thanks! > Removing of non-existent login-module finishes with outcome success > ------------------------------------------------------------------- > > Key: WFLY-6083 > URL: https://issues.jboss.org/browse/WFLY-6083 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Priority: Minor > > In case when non-existent login-module is removed through Management CLI, opertation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-416) Unable to add FileSystem realm when no relative-to attribute is provided

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-416?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-416: --------------------------- Git Pull Request: https://github.com/wildfly-security/elytron-subsystem/pull/164 (was: https://github.com/wildfly-security/elytron-subsystem/pull/177) > Unable to add FileSystem realm when no relative-to attribute is provided > ------------------------------------------------------------------------ > > Key: ELY-416 > URL: https://issues.jboss.org/browse/ELY-416 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Josef Cacek > Assignee: Pedro Igor > > The {{FileSystemRealmDefinition}} doesn't handle correctly {{"relative-to"}} attribute when it's not provided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-416) Unable to add FileSystem realm when no relative-to attribute is provided

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-416?page=com.atlassian.jira.plugin.sy... ] Pedro Igor reassigned ELY-416: ------------------------------ Assignee: Jan Kalina (was: Pedro Igor) > Unable to add FileSystem realm when no relative-to attribute is provided > ------------------------------------------------------------------------ > > Key: ELY-416 > URL: https://issues.jboss.org/browse/ELY-416 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Josef Cacek > Assignee: Jan Kalina > > The {{FileSystemRealmDefinition}} doesn't handle correctly {{"relative-to"}} attribute when it's not provided. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6360) Upgrade picketlink 2.5.5.SP1 to 2.5.5.SP2

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-6360?page=com.atlassian.jira.plugin.... ] Ivo Studensky reassigned WFLY-6360: ----------------------------------- Component/s: Security Summary: Upgrade picketlink 2.5.5.SP1 to 2.5.5.SP2 (was: Upgrade picketlink bindings 2.5.5.SP1 to 2.5.5.SP2) Affects Version/s: 10.0.0.Final Assignee: Darran Lofthouse (was: Jason Greene) > Upgrade picketlink 2.5.5.SP1 to 2.5.5.SP2 > ----------------------------------------- > > Key: WFLY-6360 > URL: https://issues.jboss.org/browse/WFLY-6360 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Bartosz Baranowski > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 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 May 2016