March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1066607|https://bugzilla.redhat.com/show_bug.cgi?id=1066607] from ON_QA to VERIFIED > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.1.Final > > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- 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

11 years, 7 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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3042: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1072312 > 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

11 years, 7 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 Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reopened WFLY-3042: ----------------------------------- > 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

11 years, 7 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 Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-3042: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/5976 (was: https://github.com/wildfly/wildfly/pull/5976, https://github.com/jbossas/jboss-eap/pull/997) > 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

11 years, 7 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 Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on WFLY-3042: --------------------------------------- [~raggz], is it enough to raise a PR for this on Wildfly, or should I raise one for EAP 6.x as well? > 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1066606|https://bugzilla.redhat.com/show_bug.cgi?id=1066606] from ON_QA to VERIFIED > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.1.Final > > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1785) TOA, inconsistent message delivery

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/JGRP-1785?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved JGRP-1785. -------------------------------- Resolution: Done Issue resolved, thanks. > TOA, inconsistent message delivery > ---------------------------------- > > Key: JGRP-1785 > URL: https://issues.jboss.org/browse/JGRP-1785 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Environment: Fedora release 17 (Beefy Miracle) > Reporter: Ryan Emerson > Assignee: Pedro Ruivo > Fix For: 3.5 > > > When sending total order messages between two nodes, for a prolonged period of time, an inconsistency is encountered when comparing each node's total order of messages. > I believe this issue is related to how sequence numbers are handled in the implementation, not the protocol itself. I appreciate that TOA is designed for environments where the subset of destinations in the network varies, however I have been unable to reproduce this error when the total number of nodes is > 2. It is still possible that this inconsistency may occur after a large amount of time when the number of nodes is > 2. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-796) LdapExtended login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-796?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-796: -------------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1067599|https://bugzilla.redhat.com/show_bug.cgi?id=1067599] from ON_QA to VERIFIED > LdapExtended login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-796 > URL: https://issues.jboss.org/browse/SECURITY-796 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_20.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-796.patch > > > LdapExtended login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-314) EE subsystem global modules should support annotation flag

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-314?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-314: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1009166|https://bugzilla.redhat.com/show_bug.cgi?id=1009166] from ON_QA to VERIFIED > EE subsystem global modules should support annotation flag > ---------------------------------------------------------- > > Key: WFLY-314 > URL: https://issues.jboss.org/browse/WFLY-314 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EE > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Annotation indexes aren't imported with modules by default, but you can specify the annotation flag in the manifest Dependencies line or the annotation attribute in jboss-deployment-structure.xml. > The EE subsystem's global modules section does not let you specify that option, which means you can't define EJB interceptors and similar things in global modules. It should let you do that. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1065515|https://bugzilla.redhat.com/show_bug.cgi?id=1065515] from ON_QA to VERIFIED > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- 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

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014