March 2014 - jboss-jira - Jboss List Archives

[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

12 years, 2 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

12 years, 2 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

12 years, 2 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3060) Rare KrbException: Request is a replay issue in negotiation tests

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3060?page=com.atlassian.jira.plugin.... ] Dominik Pospisil updated WFLY-3060: ----------------------------------- Description: The failures happend while sending second TGS-REQ ticket from client to kerberos KDC server. The cause seems to be a limitation of ApacheDS kerberos server used in the test case. The ApacheDS employs simple replay detection mechanism based on in-memory ticket cache service. The cache stores client and server credentials and ticket timestamp. Specificaly, the cache do not store ticket content. During GSS SecContext establishment, there are 2 TGS-REQ tickets sent from the client (sun.security.jgss.krb5.GSSContextSpi). First to acquire service credentials ticket and second to get SecContext ticket. The second ticket is being send immediatelly after the fisrt one. If the second (valid) ticket is sent with the same timestamp as the first one, the ApacheDS treats the second one as a false positive and throw Request is a replay kerberos exception. > Rare KrbException: Request is a replay issue in negotiation tests > ----------------------------------------------------------------- > > Key: WFLY-3060 > URL: https://issues.jboss.org/browse/WFLY-3060 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Final > Reporter: Dominik Pospisil > Assignee: Ondrej Zizka > > The failures happend while sending second TGS-REQ ticket from client to kerberos KDC server. > The cause seems to be a limitation of ApacheDS kerberos server used in the test case. The ApacheDS employs simple replay detection mechanism based on in-memory ticket cache service. The cache stores client and server credentials and ticket timestamp. Specificaly, the cache do not store ticket content. > During GSS SecContext establishment, there are 2 TGS-REQ tickets sent from the client (sun.security.jgss.krb5.GSSContextSpi). First to acquire service credentials ticket and second to get SecContext ticket. The second ticket is being send immediatelly after the fisrt one. If the second (valid) ticket is sent with the same timestamp as the first one, the ApacheDS treats the second one as a false positive and throw Request is a replay kerberos exception. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3060) Rare KrbException: Request is a replay issue in negotiation tests

by Dominik Pospisil (JIRA)

Dominik Pospisil created WFLY-3060: -------------------------------------- Summary: Rare KrbException: Request is a replay issue in negotiation tests Key: WFLY-3060 URL: https://issues.jboss.org/browse/WFLY-3060 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: 8.0.0.Final Reporter: Dominik Pospisil Assignee: Ondrej Zizka -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2773) ClientConfigurationImpl should not translate IP address to host name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2773: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1054776|https://bugzilla.redhat.com/show_bug.cgi?id=1054776] from ON_QA to VERIFIED > ClientConfigurationImpl should not translate IP address to host name > -------------------------------------------------------------------- > > Key: WFLY-2773 > URL: https://issues.jboss.org/browse/WFLY-2773 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Jan Martiska > Assignee: Jan Martiska > > When creating a ModelControllerClient and passing in an IP address, ClientConfigurationImpl internally translates it to a host name, like here: > {noformat} > public static ModelControllerClientConfiguration create(final InetAddress address, final int port) { > return new ClientConfigurationImpl(address.getHostName(), port, null, null, null, createDefaultExecutor(), true, null); > } > {noformat} > Later on, when the client connects, it is translated via DNS back to an IP address. This is not only unnecessary, but in some situations, it is wrong. > Consider a Windows machine having two IP addresses ,A and B, on one network interface, where only A is pointed at by a DNS record. > - Run AS testsuite and pass it the address B as the node0 property, AS will bind itself to this address. > - Now when a test creates a ModelControllerClient using IP address B, the address B will get translated to the host name, even though B is not in the DNS. The resolving works this way on a Windows machine. > - During the connection, the host name will get resolved by DNS to address A and the test will try to connect through address A. The connection will be refused, or worse, might connect to another instance on the same machine. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-895) JBoss crashes when run with AspectJ java agent

by dpocock (JIRA)

[ https://issues.jboss.org/browse/WFLY-895?page=com.atlassian.jira.plugin.s... ] dpocock commented on WFLY-895: ------------------------------ It looks like Jira has messaged up the formatting of that diff > JBoss crashes when run with AspectJ java agent > ---------------------------------------------- > > Key: WFLY-895 > URL: https://issues.jboss.org/browse/WFLY-895 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Environment: OS X 10.7.2, Ubuntu 11.10 > Reporter: Jack Lund > Assignee: David Lloyd > Labels: aspectj, load_time_weaving > > When trying to start JBoss with the AspectJ java agent (-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the following stack trace in the logs: > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b > JAVA: java > JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > WARNING: Failed to load the specified logmodule org.jboss.logmanager:main > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.modules.Module.run(Module.java:248) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-895) JBoss crashes when run with AspectJ java agent

by dpocock (JIRA)

[ https://issues.jboss.org/browse/WFLY-895?page=com.atlassian.jira.plugin.s... ] dpocock commented on WFLY-895: ------------------------------ Here is a full diff of the workaround involving logging settings on the JVM command line, as used to get jmxetric versions before 1.0.5 to work with JBoss: --- bin/standalone.conf +++ ../jboss-as-7.1.0.Final.for-jmxetric/bin/standalone.conf @@ -4,6 +4,7 @@ ## ## ############################################################################## +JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager" # # This file is optional; it may be removed if not needed. # @@ -48,6 +49,8 @@ # if [ "x$JAVA_OPTS" = "x" ]; then JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" + JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar -Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar -Xbootclasspath/p:$JBOSS_HOME/modules/org/apache/log4j/main/log4j-1.2.16.jar" + JAVA_OPTS="$JAVA_OPTS -javaagent:$HOME/opt/ganglia/jmxetric/jmxetric-1.0.2.jar=host=jboss-host.example.org,port=8649,wireformat31x=true,config=$HOME/opt/ganglia/jmxetric/etc/jmxetric-jboss.xml" JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS -Djboss.server.default.config=standalone.xml" else > JBoss crashes when run with AspectJ java agent > ---------------------------------------------- > > Key: WFLY-895 > URL: https://issues.jboss.org/browse/WFLY-895 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Environment: OS X 10.7.2, Ubuntu 11.10 > Reporter: Jack Lund > Assignee: David Lloyd > Labels: aspectj, load_time_weaving > > When trying to start JBoss with the AspectJ java agent (-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the following stack trace in the logs: > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b > JAVA: java > JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > WARNING: Failed to load the specified logmodule org.jboss.logmanager:main > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.modules.Module.run(Module.java:248) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-895) JBoss crashes when run with AspectJ java agent

by dpocock (JIRA)

[ https://issues.jboss.org/browse/WFLY-895?page=com.atlassian.jira.plugin.s... ] dpocock commented on WFLY-895: ------------------------------ There are some related issues in WFLY-3054 > JBoss crashes when run with AspectJ java agent > ---------------------------------------------- > > Key: WFLY-895 > URL: https://issues.jboss.org/browse/WFLY-895 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Environment: OS X 10.7.2, Ubuntu 11.10 > Reporter: Jack Lund > Assignee: David Lloyd > Labels: aspectj, load_time_weaving > > When trying to start JBoss with the AspectJ java agent (-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the following stack trace in the logs: > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b > JAVA: java > JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > WARNING: Failed to load the specified logmodule org.jboss.logmanager:main > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.modules.Module.run(Module.java:248) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more -- 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, 2 months

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