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

10 years, 9 months

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

10 years, 9 months

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

10 years, 9 months

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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3021) LogStoreDefinition exposes a bogus write-attribute handler for its 'type' attribute

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3021?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-3021. ------------------------------------ Fix Version/s: 8.0.1.Final (was: 9.0.0.CR1) Resolution: Won't Fix I forgot; WFLY-3022 is the 9.x part. > LogStoreDefinition exposes a bogus write-attribute handler for its 'type' attribute > ----------------------------------------------------------------------------------- > > Key: WFLY-3021 > URL: https://issues.jboss.org/browse/WFLY-3021 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.1.Final > > > The 'type' attribute of LogStoreResource isn't really read-write. Its value is determined by attributes of the parent resource. The OSH for write-attribute is ReloadRequiredWriteAttributeHandler, and when the reload happens whatever value is set will be lost. > For 8.0.1 I'll have the OSH just log a WARN. The attribute should be made read-only for 9. I could make it read-only for 8.0.1 but I don't want to do a management API bump, introduce transformation etc. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3021) LogStoreDefinition exposes a bogus write-attribute handler for its 'type' attribute

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3021?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3021: ----------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.1.Final) I'm going to skip the WARN part in 8.0.1 and just deal with it in 9.x. Too much hassle to get ExpressionSupportSmokeTestCase to deal with the fact that writing doesn't actually do anything. > LogStoreDefinition exposes a bogus write-attribute handler for its 'type' attribute > ----------------------------------------------------------------------------------- > > Key: WFLY-3021 > URL: https://issues.jboss.org/browse/WFLY-3021 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The 'type' attribute of LogStoreResource isn't really read-write. Its value is determined by attributes of the parent resource. The OSH for write-attribute is ReloadRequiredWriteAttributeHandler, and when the reload happens whatever value is set will be lost. > For 8.0.1 I'll have the OSH just log a WARN. The attribute should be made read-only for 9. I could make it read-only for 8.0.1 but I don't want to do a management API bump, introduce transformation etc. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2455) Cannot configure the list of recovery modules due to ArjunaRecoveryManagerService hardcoding them

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-2455?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-2455: -------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Cannot configure the list of recovery modules due to ArjunaRecoveryManagerService hardcoding them > ------------------------------------------------------------------------------------------------- > > Key: WFLY-2455 > URL: https://issues.jboss.org/browse/WFLY-2455 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Beta1 > Reporter: gui borland > Assignee: Gytis Trikleris > > Using a custom jbossts-properties.xml file defined via the com.arjuna.ats.arjuna.common.propertiesFile systemsetting, i can register a custom recovery manager for arjuna. > However, the ArjunaRecoveryManagerService class overwrite the recovery configuration mentioned in my jbossts-properties.xml file with a hardcoded list of recovery modules. > This makes me wonder if/how the hornetq recovery (org.hornetq.jms.server.recovery.HornetQXAResourceRecover) gets registered in wildfly.. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2455) Cannot configure the list of recovery modules due to ArjunaRecoveryManagerService hardcoding them

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-2455?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-2455: -------------------------------- Issue Type: Enhancement (was: Bug) > Cannot configure the list of recovery modules due to ArjunaRecoveryManagerService hardcoding them > ------------------------------------------------------------------------------------------------- > > Key: WFLY-2455 > URL: https://issues.jboss.org/browse/WFLY-2455 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Beta1 > Reporter: gui borland > Assignee: Tom Jenkinson > > Using a custom jbossts-properties.xml file defined via the com.arjuna.ats.arjuna.common.propertiesFile systemsetting, i can register a custom recovery manager for arjuna. > However, the ArjunaRecoveryManagerService class overwrite the recovery configuration mentioned in my jbossts-properties.xml file with a hardcoded list of recovery modules. > This makes me wonder if/how the hornetq recovery (org.hornetq.jms.server.recovery.HornetQXAResourceRecover) gets registered in wildfly.. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3041) Add additional packages to the sun.jdk that are expected to be available by JDBC drivers using Kerberos

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3041?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3041: ----------------------------------- Component/s: Class Loading > Add additional packages to the sun.jdk that are expected to be available by JDBC drivers using Kerberos > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-3041 > URL: https://issues.jboss.org/browse/WFLY-3041 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Class Loading > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > A couple of additional packages are required, nothing really special either siblings or children of packages we already list. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3041) Add additional packages to the sun.jdk that are expected to be available by JDBC drivers using Kerberos

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3041: -------------------------------------- Summary: Add additional packages to the sun.jdk that are expected to be available by JDBC drivers using Kerberos Key: WFLY-3041 URL: https://issues.jboss.org/browse/WFLY-3041 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.CR1 A couple of additional packages are required, nothing really special either siblings or children of packages we already list. -- 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

10 years, 9 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 February 2014