July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Forum Reference: https://lists.jboss.org/pipermail/keycloak-dev/2018-July/010985.html, https://lists.jboss.org/pipermail/wildfly-dev/2018-July/006601.html, https://lists.jboss.org/pipermail/wildfly-dev/2018-May/006511.html (was: https://lists.jboss.org/pipermail/keycloak-dev/2018-July/010985.html, https://lists.jboss.org/pipermail/wildfly-dev/2018-July/006601.html) > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > > Add > {code} > node-identifier="${jboss.tx.node.id:1} > {code} > to the default WF Config files. > Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-490) Upgrade EMF to 2.8.0 or higher

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-490?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-490: ----------------------------------------- Yes, it is. > Upgrade EMF to 2.8.0 or higher > ------------------------------ > > Key: DROOLS-490 > URL: https://issues.jboss.org/browse/DROOLS-490 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.1.0.Beta3 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > Currently we use emf 2.6 with emf xmi 2.5. That's risky. > For more info, see https://github.com/jboss-integration/jboss-integration-platform-bom/pull/... > 1) Upgrade us to at least 2.7.0.v20120123-0926, but preferably 2.8, 2.9 or higher > 2) Send a PR to the ip-bom to change the emf version. > Undo the extra emf xmi version introduced in this pull request: > https://github.com/jboss-integration/jboss-integration-platform-bom/pull/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-490) Upgrade EMF to 2.8.0 or higher

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-490?page=com.atlassian.jira.plugin... ] Geoffrey De Smet edited comment on DROOLS-490 at 7/10/18 10:44 AM: ------------------------------------------------------------------- Yes, it is. Unless we can get rid of the emf usage all together. was (Author: ge0ffrey): Yes, it is. > Upgrade EMF to 2.8.0 or higher > ------------------------------ > > Key: DROOLS-490 > URL: https://issues.jboss.org/browse/DROOLS-490 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.1.0.Beta3 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > Currently we use emf 2.6 with emf xmi 2.5. That's risky. > For more info, see https://github.com/jboss-integration/jboss-integration-platform-bom/pull/... > 1) Upgrade us to at least 2.7.0.v20120123-0926, but preferably 2.8, 2.9 or higher > 2) Send a PR to the ip-bom to change the emf version. > Undo the extra emf xmi version introduced in this pull request: > https://github.com/jboss-integration/jboss-integration-platform-bom/pull/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Description: Add {code} node-identifier="${jboss.tx.node.id:1} {code} to the default WF Config files. Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script was: Add node-identifier="${jboss.tx.node.id:1} to the default WF Config files. Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > > Add > {code} > node-identifier="${jboss.tx.node.id:1} > {code} > to the default WF Config files. > Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Description: Add node-identifier="${jboss.tx.node.id:1} to the default WF Config files. Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > > Add node-identifier="${jboss.tx.node.id:1} to the default WF Config files. > Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on WFLY-10541: -------------------------------------- They do have different meanings but it would be useful to provide a way to override the node-identifier with a system property > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Forum Reference: https://lists.jboss.org/pipermail/keycloak-dev/2018-July/010985.html, https://lists.jboss.org/pipermail/wildfly-dev/2018-July/006601.html (was: https://lists.jboss.org/pipermail/keycloak-dev/2018-July/010985.html) > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Summary: allow user to easily override the transaction node identifier (was: default transactions node-identifier to jboss.node.name) > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Jason Greene > > It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. > {code} > WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > {code} > {code} > <subsystem xmlns="urn:jboss:domain:transactions:3.0"> > <core-environment node-identifier="${jboss.node.name}"> > {code} > I was thinking messaging also had property that needed to be set but I am not seeing the warning currently. Also I have seen if jboss.node.name is not set, then ejb calls may not work as expected, so it would be good to have it warn if it is not set as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Description: (was: It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. {code} WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. {code} {code} <subsystem xmlns="urn:jboss:domain:transactions:3.0"> <core-environment node-identifier="${jboss.node.name}"> {code} I was thinking messaging also had property that needed to be set but I am not seeing the warning currently. Also I have seen if jboss.node.name is not set, then ejb calls may not work as expected, so it would be good to have it warn if it is not set as well.) > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson commented on WFLY-10541: -------------------------------------- >From Brad: It is very common for environments to run multiple Wildfly instances on the same machine, it would be good to use 1 property such as jboss.node.name as a default for jboss.tx.node.id / node-identifier and any other property that needs to be unique when Wildfly instances are stacked on a machine. {code} WARN [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. {code} {code} <subsystem xmlns="urn:jboss:domain:transactions:3.0"> <core-environment node-identifier="${jboss.node.name}"> {code} I was thinking messaging also had property that needed to be set but I am not seeing the warning currently. Also I have seen if jboss.node.name is not set, then ejb calls may not work as expected, so it would be good to have it warn if it is not set as well. > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 July 2018