January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4301) Quickstart ejb-multi-server does not work

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-4301: -------------------------------------- Summary: Quickstart ejb-multi-server does not work Key: WFLY-4301 URL: https://issues.jboss.org/browse/WFLY-4301 Project: WildFly Issue Type: Bug Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink After changing the maven artifactId of the project the created application ear/war files are named different and the deployment script deploy-domain.cli will not work. Also the ejb lookup names has change because of this and need to be adapted. related commit 10f95488c0a6f765c25d70a7dcbd566e59230fd2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4300) Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-4300: -------------------------------------- Summary: Different behaviour for jboss-ejb-client.xml configuration when undeploy/deploy or server restart Key: WFLY-4300 URL: https://issues.jboss.org/browse/WFLY-4300 Project: WildFly Issue Type: Bug Affects Versions: 9.0.0.Alpha1 Reporter: Wolf-Dieter Fink Assignee: Jason Greene If remote-outbound-connection to a cluster is used and the application contain a jboss-ejb-client.xml with <clusters> element and this element must be changed a simple undeploy/deploy will not change the behavior. A full server restart is needed! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4299) transaction subsystem node-identifier can not resolve expression

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-4299?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-4299: ---------------------------------------- Seems like a general issue for expression use in domain mode as the same appears if remote-outbound-conection user contain an expression. Will not be resolved as in former builds > transaction subsystem node-identifier can not resolve expression > ---------------------------------------------------------------- > > Key: WFLY-4299 > URL: https://issues.jboss.org/browse/WFLY-4299 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Brian Stansberry > Priority: Critical > Labels: configuration, configuration_management, domain > > If the transaction subsystem should use an expression as node-identifier this will not work in domain mode: > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 36) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "WFLYCTL0211: Cannot resolve expression '${txNodeIdentifier}'" > This was possible in former builds with the same configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2879) Remove duplicated code from test cases where custom modules are needed

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-2879?page=com.atlassian.jira.plugin.... ] Pedro Igor updated WFLY-2879: ----------------------------- Fix Version/s: 9.0.0.Alpha1 > Remove duplicated code from test cases where custom modules are needed > ---------------------------------------------------------------------- > > Key: WFLY-2879 > URL: https://issues.jboss.org/browse/WFLY-2879 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 9.0.0.Alpha1 > > > When writing some integration tests for the PicketLink subsystem, I've noticed that there is no utility class or API to make easier create and remove custom modules from the modules directory. > There are a few tests with this requirement, and most of them are replicating code. > After discussing with [~kabirkhan], he suggested to open this JIRA to review those test cases and make them use a reusable component to work with custom modules. > I've already wrote a class that I think can satisfy all test cases requiring a custom module. > See https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration.... > Usage example: https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Yacine Jaber (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Yacine Jaber updated DROOLS-702: -------------------------------- Attachment: wod-drools-test.7z > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Mark Proctor > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Yacine Jaber (JIRA)

Yacine Jaber created DROOLS-702: ----------------------------------- Summary: Rule Inheritance fired the sub rule even the condition doen't match Key: DROOLS-702 URL: https://issues.jboss.org/browse/DROOLS-702 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final Environment: Windows, Java6.0.29 Reporter: Yacine Jaber Assignee: Mark Proctor Priority: Critical You can find the attached a simple maven project that shows this error. You can run ExampleDrools class as main java application. The sub rules are fired even if the condition is not matched. There are a work arround by using <from $fact> into a sub rule to avoid firing this one. This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2640) Implement support for group-by (if an explicit construct is necessary) and distinct

by tushar sarde (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2640?page=com.atlassian.jira.plug... ] tushar sarde commented on JBRULES-2640: --------------------------------------- Any Update > Implement support for group-by (if an explicit construct is necessary) and distinct > ----------------------------------------------------------------------------------- > > Key: JBRULES-2640 > URL: https://issues.jboss.org/browse/JBRULES-2640 > Project: JBRULES > Issue Type: Feature Request > Components: All > Affects Versions: 5.1.0.FINAL > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Labels: fusion_roadmap > Fix For: FUTURE > > > Implement support for group-by (if an explicit construct is necessary) and distinct -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-694) accumulate with sliding window and other LHS condition

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-694?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-694. -------------------------------- Fix Version/s: 6.2.0.Final Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/fa05dcc5d > accumulate with sliding window and other LHS condition > ------------------------------------------------------ > > Key: DROOLS-694 > URL: https://issues.jboss.org/browse/DROOLS-694 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR4 > Environment: fail with PHREAK, work correctly as expected with RETEOO > Reporter: Matteo Mortari > Assignee: Mario Fusco > Fix For: 6.2.0.Final > > Attachments: 20150121.accumulate-window-counter.zip > > > With reference to attached reproducer. > Assuming the following KB, where to goal is to keep a {{Counter}} fact for the amount of {{Measurement}} events received in the last hour. > {code:java} > declare Measurement > @role(event) > end > rule "Init Counter last 1h" > agenda-group "USERSPACE" > salience 1 > no-loop > when > not Counter( name == "Counter last 1h" ) > then > Counter c = new Counter("Counter last 1h", 0); > insert(c); > System.out.println("RHS Init Counter last 1h " + c); > end > rule "Update Counter last 1h" > agenda-group "USERSPACE" > no-loop > when > accumulate( $token : Measurement() over window:time( 1h ) ; > $val : count($token) > ) > $cv1 : Counter( name == "Counter last 1h", value != $val.doubleValue() ) > then > int count = $val.intValue(); > $cv1.setValue(count); > update($cv1); > System.out.println("RHS Update Counter last 1h : "+$cv1); > end > {code} > The following Unit test shall have the effect in the end to obtain value 2.0 in the {{Counter}} object, as I've inserted 2 {{MEasurement}} within the last hour and within two minutes > {code:java} > advance(clock, 1, TimeUnit.MINUTES); > insert(session, new Measurement("voltage", "220")); > fire(session); > advance(clock, 1, TimeUnit.MINUTES); > insert(session, new Measurement("voltage", "221")); > fire(session); > LOG.info("Final checks"); > Counter counter = (Counter) session.getObjects(counterFilter).iterator().next(); // I'm taking a shortcut as for this reproducer I know there is only 1 Counter in WM > assertEquals("I've inserted 2 Measurement within the hour ", 2, counter.getValue(), 0); > {code} > However this works only with ReteOO and the test FAILS with Phreak. > Can you kindly advise, please? > Thank you > MM -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4299) transaction subsystem node-identifier can not resolve expression

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-4299?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated WFLY-4299: ----------------------------------- Priority: Critical (was: Major) > transaction subsystem node-identifier can not resolve expression > ---------------------------------------------------------------- > > Key: WFLY-4299 > URL: https://issues.jboss.org/browse/WFLY-4299 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Brian Stansberry > Priority: Critical > Labels: configuration, configuration_management, domain > > If the transaction subsystem should use an expression as node-identifier this will not work in domain mode: > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 36) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "WFLYCTL0211: Cannot resolve expression '${txNodeIdentifier}'" > This was possible in former builds with the same configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4299) transaction subsystem node-identifier can not resolve expression

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-4299: -------------------------------------- Summary: transaction subsystem node-identifier can not resolve expression Key: WFLY-4299 URL: https://issues.jboss.org/browse/WFLY-4299 Project: WildFly Issue Type: Bug Components: Domain Management Affects Versions: 9.0.0.Alpha1 Reporter: Wolf-Dieter Fink Assignee: Brian Stansberry If the transaction subsystem should use an expression as node-identifier this will not work in domain mode: ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 36) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "WFLYCTL0211: Cannot resolve expression '${txNodeIdentifier}'" This was possible in former builds with the same configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 2 months

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 January 2015