June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1590) The behavior of rule flow is different in drools 6.4.0 Final and 6.5.0 Final

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1590?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1590: ----------------------------------- Sprint: 2017 Week 22-23 (was: 2017 Week 22-23) > The behavior of rule flow is different in drools 6.4.0 Final and 6.5.0 Final > ---------------------------------------------------------------------------- > > Key: DROOLS-1590 > URL: https://issues.jboss.org/browse/DROOLS-1590 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: GaoShengwei GaoShengwei > Assignee: Mario Fusco > Attachments: BaiduHi_2017-5-31_18-1-18.png, BaiduHi_2017-5-31_18-2-54.png > > > I am using drools 6.5.0 Final. When I run sample code of section "starting a ruleflow from a rule" in documentation (https://nheron.gitbooks.io/droolsonboarding/content/gettingStarted/lesson...), the output sequence is different from the screenshot. > But when I switched to drools version to 6.4.0 Final, the output sequence was extactly same with screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1591) Problems in serialization/deserialization of KnowledgePackages

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1591?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1591: ----------------------------------- Sprint: 2017 Week 22-23 (was: 2017 Week 22-23) > Problems in serialization/deserialization of KnowledgePackages > -------------------------------------------------------------- > > Key: DROOLS-1591 > URL: https://issues.jboss.org/browse/DROOLS-1591 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.0.0.Beta3 > Reporter: Vítor Moreira > Assignee: Mario Fusco > Attachments: jboss_issue.tar.gz > > > Using {{DroolsStreamUtils}}, created an unit-test to serialize and deserialize a DRL file. In version "6.0.1.Final", the unit-test runs flawlessly. In other versions, deserialization gives an ClassNotFoundException for the declared event. > I've checked StackOverflow and Drools' JIRA for similar problems and found nothing. > I've also attached a junit. Please change property {{drools.version}} to test with different Drools versions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1589) ClassCastException using oopath in 2 distinct rules

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1589?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1589: ----------------------------------- Sprint: 2017 Week 22-23 (was: 2017 Week 22-23) > ClassCastException using oopath in 2 distinct rules > --------------------------------------------------- > > Key: DROOLS-1589 > URL: https://issues.jboss.org/browse/DROOLS-1589 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2900) Cut memory use by AttributeDefinition.arbitraryDescriptors

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2900: ---------------------------------------- Summary: Cut memory use by AttributeDefinition.arbitraryDescriptors Key: WFCORE-2900 URL: https://issues.jboss.org/browse/WFCORE-2900 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Currently AttributeDefinition.arbitraryDescriptors is: private final Map<String, ModelNode> arbitraryDescriptors = new HashMap<>(); In most cases that can be Collections.emptyMap(), and if not it can be an unmodifiable map saving the need to allocate an unmodifiable wrapper every time the getter is called. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8873) Provide information how to configure node identifier in "...Node identifier property is set to the default value..." warning

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-8873?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned WFLY-8873: ------------------------------------- Assignee: Ondra Chaloupka (was: Tom Jenkinson) > Provide information how to configure node identifier in "...Node identifier property is set to the default value..." warning > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8873 > URL: https://issues.jboss.org/browse/WFLY-8873 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > If EAP 7 is started then there is logged warning like: > {code} > 13:03:30,260 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > {code} > There should be provided information what it means for example by providing link to documentation and how to configure it in CLI. {{node-identifier}} can be set in CLI using: > {{/subsystem=transactions:write-attribute(name=node-identifier,value=unique-value)}} command -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8873) Provide information how to configure node identifier in "...Node identifier property is set to the default value..." warning

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created WFLY-8873: ------------------------------------- Summary: Provide information how to configure node identifier in "...Node identifier property is set to the default value..." warning Key: WFLY-8873 URL: https://issues.jboss.org/browse/WFLY-8873 Project: WildFly Issue Type: Bug Components: Transactions Reporter: Ondra Chaloupka Assignee: Tom Jenkinson Priority: Minor If EAP 7 is started then there is logged warning like: {code} 13:03:30,260 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. {code} There should be provided information what it means for example by providing link to documentation and how to configure it in CLI. {{node-identifier}} can be set in CLI using: {{/subsystem=transactions:write-attribute(name=node-identifier,value=unique-value)}} command -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3977) Properties file used for property substitution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3977?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-3977: ---------------------------------------- I never answered the last question. The META-INF/jboss.properties file is not used for any other purpose besides this expression resolution during application deployment. > Properties file used for property substitution > ----------------------------------------------- > > Key: WFLY-3977 > URL: https://issues.jboss.org/browse/WFLY-3977 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 8.1.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Brian Stansberry > > Customer is deploying multiple copies of the same applicaiton but each copy has differnet set of locations. They can use properties substituaiton in annoatations but that works only with global properties that are defined at global level. They would like to be able to supply a properties file with each deployment that would be used for properties substitution during deployment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2899) not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2899?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2899: -------------------------------------- Steps to Reproduce: Setup mixed domain, I used WildFly 11 Alpha master and EAP 6.3.0.GA slave, used default profile copied from EAP6 and renamed to eap6-default # start master {{jboss-eap-7.1/bin/domain.sh --host-config=host-master.xml}} # start slave - one server in group eap6-main-server-group {{jboss-eap-6.3/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999}} connect to DC with CLI # deploy war {{deploy ~/Downloads/simple-servlet.war --server-groups=eap6-main-server-group}} # add deployment overlay {{deployment-overlay add --name=overlay-test --content=WEB-INF/web.xml=/tmp/web.xml --server-groups=eap6-main-server-group --deployments=simple-servlet.war}} # redeploy affected (optional, there is the same error without redeploy) {{deployment-overlay redeploy-affected --name=overlay-test}} # try to remove deployment-overlay {{deployment-overlay remove --name=overlay-test}} was: Setup mixed domain, I used EAP 7.1.0.DR17 master and EAP 6.3.0.GA slave, used default profile copied from EAP6 and renamed to eap6-default follow instructions in [documentation|https://doc-stage.usersys.redhat.com/documentation/en-us/re...] # start master {{jboss-eap-7.1/bin/domain.sh --host-config=host-master.xml}} # start slave - one server in group eap6-main-server-group {{jboss-eap-6.3/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999}} connect to DC with CLI # deploy war {{deploy ~/Downloads/simple-servlet.war --server-groups=eap6-main-server-group}} # add deployment overlay {{deployment-overlay add --name=overlay-test --content=WEB-INF/web.xml=/tmp/web.xml --server-groups=eap6-main-server-group --deployments=simple-servlet.war}} # redeploy affected (optional, there is the same error without redeploy) {{deployment-overlay redeploy-affected --name=overlay-test}} # try to remove deployment-overlay {{deployment-overlay remove --name=overlay-test}} > not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-2899 > URL: https://issues.jboss.org/browse/WFCORE-2899 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Beta23 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Blocker > > It's not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older. The error is: > {noformat} > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"eap6-server-group" => {"host" => {"msimka-t450.brq.redhat.com" => {"server-one" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014762: Removing services has lead to unsatisfied dependencies: > Service jboss.deploymentOverlayIndexService.deploymentOverlayService.overlay-test was depended upon by service jboss.deploymentOverlayIndexService.deploymentOverlayService.contentService.overlay-test.\"WEB-INF/web.xml\", service jboss.deploymentOverlayIndexService.deploymentOverlayLinkService.overlay-test.\"simple-servlet.war\""}}}}}}}} > {noformat} > It works when slave is EAP 6.4.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2899) not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2899?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved JBEAP-11286 to WFCORE-2899: --------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2899 (was: JBEAP-11286) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management (was: Domain Management) Affects Version/s: 3.0.0.Beta23 (was: 7.1.0.DR17) Affects Testing: (was: Regression) > not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-2899 > URL: https://issues.jboss.org/browse/WFCORE-2899 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Beta23 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Blocker > > It's not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older. The error is: > {noformat} > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"eap6-server-group" => {"host" => {"msimka-t450.brq.redhat.com" => {"server-one" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014762: Removing services has lead to unsatisfied dependencies: > Service jboss.deploymentOverlayIndexService.deploymentOverlayService.overlay-test was depended upon by service jboss.deploymentOverlayIndexService.deploymentOverlayService.contentService.overlay-test.\"WEB-INF/web.xml\", service jboss.deploymentOverlayIndexService.deploymentOverlayLinkService.overlay-test.\"simple-servlet.war\""}}}}}}}} > {noformat} > It works when slave is EAP 6.4.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8868) per application Expressions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8868?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8868: ---------------------------------------- Something along these lines is already supported -- see my comment on https://issues.jboss.org/browse/WFLY-3977 A META-INF/jboss.properties file in the deployment, or added as a deployment-overlay, will let you add properties to the expression resolution. I'm not sure if that's described anywhere in WildFly documentation. A bit of googling didn't show anything. :( The https://docs.jboss.org/author/display/WFLY10/Expressions page is a child page of the docs on developing subsystems, so it's focused on expression resolution during handling of management operations or during standalone.xml etc config file processing during boot. In that context, the META-INF/jboss.properties mechanism is not available. > per application Expressions > --------------------------- > > Key: WFLY-8868 > URL: https://issues.jboss.org/browse/WFLY-8868 > Project: WildFly > Issue Type: Feature Request > Reporter: Juergen Weber > Assignee: Jason Greene > > Wildfly supports Expression Substitution in descriptors [1]. These expressions are server global. > This should be enhanced to support application scoped expressions: > ${this:aProperty} > It would be especially useful for Message Driven Beans, as an ActivationConfigProperty can only be set in a descriptor or via an annotation, but not in application code, so ActivationConfigProperties are effectively fixed. > Then you could deploy the same Message Driven Bean multiple times with a different name: > myMDB1.ear > myMDB2.ear > having > <activation-config-property-value>${this:queuename}</activation-config-property-value> > and define > <application-properties> > <application name="myMDB_DEV_QUEUE_1.ear"> > <property name="queuename" value="DEV_QUEUE_1"/> > </application> > <application name="myMDB_DEV_QUEUE_2.ear"> > <property name="queuename" value="DEV_QUEUE_2"/> > </application> > </application-properties> > whereas for production the queuename properties would be different. > [1] https://docs.jboss.org/author/display/WFLY10/Expressions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 June 2017