November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-657) Salience ignored when no-loop set

by Sebastien Chassande (JIRA)

[ https://issues.jboss.org/browse/DROOLS-657?page=com.atlassian.jira.plugin... ] Sebastien Chassande commented on DROOLS-657: -------------------------------------------- You can download from my dropbox a simple Java/Eclipse/Maven project showing the bug : https://www.dropbox.com/s/7j8w7ejehe140td/saliencebug_projet.zip?dl=0 > Salience ignored when no-loop set > --------------------------------- > > Key: DROOLS-657 > URL: https://issues.jboss.org/browse/DROOLS-657 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows x64, java 7, eclipse > Reporter: Sebastien Chassande > Assignee: Mark Proctor > Priority: Blocker > Labels: no-loop, salience > > Hello, > When we define the no-loop attribute on rules the salience is ignored. The rule execution order is the declaration order. > Best regards, > Seb -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-657) Salience ignored when no-loop set

by Sebastien Chassande (JIRA)

Sebastien Chassande created DROOLS-657: ------------------------------------------ Summary: Salience ignored when no-loop set Key: DROOLS-657 URL: https://issues.jboss.org/browse/DROOLS-657 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final Environment: Windows x64, java 7, eclipse Reporter: Sebastien Chassande Assignee: Mark Proctor Priority: Blocker Hello, When we define the no-loop attribute on rules the salience is ignored. The rule execution order is the declaration order. Best regards, Seb -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4130) check for -secmgr in appclient

by Scott Marlow (JIRA)

Scott Marlow created WFLY-4130: ---------------------------------- Summary: check for -secmgr in appclient Key: WFLY-4130 URL: https://issues.jboss.org/browse/WFLY-4130 Project: WildFly Issue Type: Feature Request Components: Application Client, Security Manager Reporter: Scott Marlow Assignee: James Perkins Fix For: 9.0.0.Beta1 We are currently getting a TCK failure due to the security manager not being enabled in our application client container. We can pass the -secmgr option if that could be handled in the app container. Current TCK error (in ejb30/sec/permsxml: {quote} ERROR: Security Manager is NOT enabled and must be for these tests. If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled. {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-654) Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-654?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-654: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-654 > URL: https://issues.jboss.org/browse/DROOLS-654 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR2 > Environment: Ubuntu Linux > Reporter: Tihomir Meščić > Assignee: Mario Fusco > Priority: Blocker > > I'm creating my {{KieSession}} by setting {{STREAM}} as the event processing mode in the configuration: > {{KieBaseConfiguration config = KieServices.Factory.get()}} > {{.newKieBaseConfiguration();}} > {{config.setOption(EventProcessingOption.STREAM);}} > > {{KieContainer kc = ks.newKieContainer( ... releaseId ... );}} > {{KieSession ksession = kc.newKieBase(config).newKieSession();}} > After that, everything works fine. But when I try to dynamically update to a new version (containing new rules): > {{kc.updateToVersion( ... newReleaseId... );}} > It seems like all of the facts are removed from the session, and my rules are no longer triggered. > When I do not use the configuration object when creating the session and just use: > {{KieSession ksession = kc.newKieSession();}} > then, everything works as expected. However, this is not an option because I need a way to specify the processing mode as {{STREAM}} (and this is the only way I know of). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-286) The SecurityRealmService should only perform a generic mapping to RealmUser if really required.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-286: --------------------------------------- Summary: The SecurityRealmService should only perform a generic mapping to RealmUser if really required. Key: WFCORE-286 URL: https://issues.jboss.org/browse/WFCORE-286 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha13 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha14 If there is a more accurate way to calculate the RealmUser then use it. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4013) The value of the bound attribute in socket-binding-group messaging is always false

by Kyle Lape (JIRA)

[ https://issues.jboss.org/browse/WFLY-4013?page=com.atlassian.jira.plugin.... ] Kyle Lape updated WFLY-4013: ---------------------------- Forum Reference: (was: https://c.na7.visual.force.com/apex/Case_View?sbstr=01264236) > The value of the bound attribute in socket-binding-group messaging is always false > ---------------------------------------------------------------------------------- > > Key: WFLY-4013 > URL: https://issues.jboss.org/browse/WFLY-4013 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: JBoss AS7 7.2.0.Final > Environment: JBoss EAP 6.3.1. > Reporter: Tom Ross > Assignee: Jeff Mesnil > > The value of bound attribute in messaging socket group is always false. > {noformat} > /socket-binding-group=standard-sockets/socket-binding=messaging:read-resource(include-runtime=true, recursive=true) > { > "outcome" => "success", > "result" => { > "bound" => false, > "bound-address" => undefined, > "bound-port" => undefined, > "client-mappings" => undefined, > "fixed-port" => false, > "interface" => undefined, > "multicast-address" => undefined, > "multicast-port" => undefined, > "name" => "messaging", > "port" => 5445 > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4054) Unexpected attribute can be added to elements in Transactions Subsystem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4054?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4054: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1156032|https://bugzilla.redhat.com/show_bug.cgi?id=1156032] from ASSIGNED to MODIFIED > Unexpected attribute can be added to elements in Transactions Subsystem > ----------------------------------------------------------------------- > > Key: WFLY-4054 > URL: https://issues.jboss.org/browse/WFLY-4054 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > > If you add unexpected argument to element in standalone.xml then it's expected to get error of "Unexpected attribute '...' encountered" [1] when server is started. > When you add a random argument to some of the elements in transactions then no error is thrown. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-242) the deployment content is deleted if first undeploy and then deploy the same application using CLI batch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-242?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-242: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1162444|https://bugzilla.redhat.com/show_bug.cgi?id=1162444] from POST to MODIFIED > the deployment content is deleted if first undeploy and then deploy the same application using CLI batch > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-242 > URL: https://issues.jboss.org/browse/WFCORE-242 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Reporter: Jay Kumar SenSharma > Assignee: Emmanuel Hugonnet > Priority: Minor > > - If deploy and undeploy CLI commands executed in a batch mode then it causes missing deployment inside the "data/content" directory which leads to the following error: > {code} > [Host Controller] 10:33:42,387 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "example.war")]) - failure description: "WFLYDC0058: No deployment content with hash d85f1e3106bc8a49838a0dccae9e80819c25e02c is available in the deployment content repository for deployment 'example.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 10:33:42,390 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4129) The RemotingLoginModule should first check if there is already a RealmUser

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-4129: -------------------------------------- Summary: The RemotingLoginModule should first check if there is already a RealmUser Key: WFLY-4129 URL: https://issues.jboss.org/browse/WFLY-4129 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 9.0.0.Alpha1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta1 The reason is because the realm may have actually already substituted in a different name for the user. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-283) SASL_SERVER and SASL_PROTOCOL options not being passed all the way to Remoting

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-283?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-283: ------------------------------------------------ Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1168313|https://bugzilla.redhat.com/show_bug.cgi?id=1168313] from ASSIGNED to POST > SASL_SERVER and SASL_PROTOCOL options not being passed all the way to Remoting > ------------------------------------------------------------------------------ > > Key: WFCORE-283 > URL: https://issues.jboss.org/browse/WFCORE-283 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Remoting, Security > Affects Versions: 1.0.0.Alpha13 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014