February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-3042: ----------------------------------- Given how hard it can be to maintain unique numerical identifiers, especially in a large environment, perhaps it's a good idea to allow a pluggable assignment strategy. Here are some ideas: * Central registry such as... ** LDAP database ** DNS entry ** JDBC data store * Perfect or imperfect hashing strategy such as... ** IP address mapping ** MAC address mapping ** Hardware serial number mapping > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3043) Clean up messaging subsystem XML configuration

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-3043: --------------------------------- Summary: Clean up messaging subsystem XML configuration Key: WFLY-3043 URL: https://issues.jboss.org/browse/WFLY-3043 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: JMS Affects Versions: 8.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 9.0.0.CR1 The messaging subsystem XML configuration defines several elements whose values correspond to the management model default values. There is no benefit to configure the default values in the XML beside showing that the configuration exists. Now that the XSD is properly annotated, the XML configuration we ship should only define values that diverges from the default ones. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2205) Undeployment prints null

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2205?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2205: ------------------------------ Fix Version/s: 8.0.1.Final > Undeployment prints null > ------------------------ > > Key: WFLY-2205 > URL: https://issues.jboss.org/browse/WFLY-2205 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.Beta1 > Reporter: Jesper Pedersen > Assignee: Tomaz Cerar > Fix For: 8.0.1.Final > > > The following is printed during a shutdown of an .ear > {noformat} > 11:21:52,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: msginflow1_mdb_msginflow_ejb.jar) in 16ms > 11:21:52,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment null (runtime-name: msginflow_mdb_msginflow_ejb.jar) in 16ms > 11:21:52,262 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment msginflow_mdb.ear (runtime-name: msginflow_mdb.ear) in 18ms > 11:21:52,387 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "msginflow_mdb.ear" (runtime-name: "msginflow_mdb.ear") > {noformat} > The 'null' part of the .jar undeployment doesn't look nice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3040) Missing modules

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3040?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-3040: ----------------------------------- How is this related to WildFly? If this is osgi problem create it in osgi jira project https://issues.jboss.org/browse/JBOSGI if you want we can move this there. > Missing modules > --------------- > > Key: WFLY-3040 > URL: https://issues.jboss.org/browse/WFLY-3040 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OSGi > Affects Versions: 8.0.0.Final > Environment: Windows 64 bits > Reporter: David Cabillic > Assignee: Thomas Diesler > > I listed modules with links to missing ones : > || module || missing module || > | org.infinispan.client.hotrod | com.google.protobuf | > | org.jboss.as.aggregate | org.jboss.as.managed-beans | > | org.jboss.genericjms | org.jboss.genericjms.provider | -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-3042: -------------------------------- Issue Type: Enhancement (was: Feature Request) > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-3042: ------------------------------------- Great recommendation, hopefully Gytis will be able to get this one into the next WildFly release. > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-3042: -------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by Tom Ross (JIRA)

Tom Ross created WFLY-3042: ------------------------------ Summary: There should be a warning logged if the default value of node identifier has not been changed. Key: WFLY-3042 URL: https://issues.jboss.org/browse/WFLY-3042 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transactions Affects Versions: 8.0.0.Final Environment: JBoss EAP 6.x Reporter: Tom Ross Assignee: Tom Jenkinson JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3022) Make LogStoreResource's 'type' attribute read-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3022?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3022: ----------------------------------- Parent: (was: WFLY-3021) Issue Type: Bug (was: Sub-task) > Make LogStoreResource's 'type' attribute read-only > -------------------------------------------------- > > Key: WFLY-3022 > URL: https://issues.jboss.org/browse/WFLY-3022 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > See parent issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3022) Make LogStoreResource's 'type' attribute read-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3022?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-3022: ---------------------------------------- Fix for this is at https://github.com/bstansberry/wildfly/compare/master...WFLY-3022 -- ready to go once master switches to 9.x work. > Make LogStoreResource's 'type' attribute read-only > -------------------------------------------------- > > Key: WFLY-3022 > URL: https://issues.jboss.org/browse/WFLY-3022 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > See parent issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

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 February 2014