January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4240) add-user.sh - if password contains § it is not possible to log into the webinterface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-4240?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-4240: -------------------------------------- Assignee: Darran Lofthouse (was: Thomas Diesler) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFLY-4240 > URL: https://issues.jboss.org/browse/WFLY-4240 > Project: WildFly > Issue Type: Bug > Components: ConfigAdmin > Affects Versions: 8.2.0.Final > Environment: wheezy, Firefox 34.0.5 > Reporter: do ev > Assignee: Darran Lofthouse > Priority: Trivial > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4240) add-user.sh - if password contains § it is not possible to log into the webinterface

by do ev (JIRA)

[ https://issues.jboss.org/browse/WFLY-4240?page=com.atlassian.jira.plugin.... ] do ev updated WFLY-4240: ------------------------ Environment: wheezy, Firefox 34.0.5 (was: wheezy) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFLY-4240 > URL: https://issues.jboss.org/browse/WFLY-4240 > Project: WildFly > Issue Type: Bug > Components: ConfigAdmin > Affects Versions: 8.2.0.Final > Environment: wheezy, Firefox 34.0.5 > Reporter: do ev > Assignee: Thomas Diesler > Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4240) add-user.sh - if password contains § it is not possible to log into the webinterface

by do ev (JIRA)

do ev created WFLY-4240: --------------------------- Summary: add-user.sh - if password contains § it is not possible to log into the webinterface Key: WFLY-4240 URL: https://issues.jboss.org/browse/WFLY-4240 Project: WildFly Issue Type: Bug Components: ConfigAdmin Affects Versions: 8.2.0.Final Environment: wheezy Reporter: do ev Assignee: Thomas Diesler Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-492) fix JMX ObjectNameAddressUtil#toPathAddress

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-492?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-492: ------------------------------------------------ Ondřej Kalman <okalman(a)redhat.com> changed the Status of [bug 1113908|https://bugzilla.redhat.com/show_bug.cgi?id=1113908] from ON_QA to VERIFIED > fix JMX ObjectNameAddressUtil#toPathAddress > ------------------------------------------- > > Key: WFCORE-492 > URL: https://issues.jboss.org/browse/WFCORE-492 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 1.0.0.Alpha15 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 1.0.0.Alpha16 > > > The code in ObjectNameAddressUtil#toPathAddress is wrong: it must look for the childAddress's submodel, not the address of the registry itself. > The current code fails with the exception: > org.jboss.as.controller._private.OperationFailedRuntimeException: WFLYCTL0071: Duplicate path element 'subsystem' found [ "WFLYCTL0071: Duplicate path element 'subsystem' found" ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4239) Support Locale.forLanguageTag()

by Romain Pelisse (JIRA)

Romain Pelisse created WFLY-4239: ------------------------------------ Summary: Support Locale.forLanguageTag() Key: WFLY-4239 URL: https://issues.jboss.org/browse/WFLY-4239 Project: WildFly Issue Type: Feature Request Components: Localization Affects Versions: 9.0.0.Alpha1 Environment: JDK 7 Reporter: Romain Pelisse Assignee: Romain Pelisse Priority: Minor The rules for Locale are different in JDK 6 vs 7, and this getLocale() method was written to conform to the JDK 6 rules. Hence it assumes 2 chars for language, 2 chars for country. Beginning with JDK 7 things are much more complex, and we don't support that. The language can be up to 8 chars, country can be [a-zA-Z]{2} | [0-9]{3}, there's the "script" element, and most importantly, Locale.forLanguageTag(). It would be nice to at least support Locale.forLanguageTag(). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1904) Usage of vault for system-properties throws java.lang.SecurityException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1904?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1904: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1174871|https://bugzilla.redhat.com/show_bug.cgi?id=1174871] from ON_QA to VERIFIED > Usage of vault for system-properties throws java.lang.SecurityException > ----------------------------------------------------------------------- > > Key: WFLY-1904 > URL: https://issues.jboss.org/browse/WFLY-1904 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.0.0.Beta1 > Reporter: Navin Surtani > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1, 8.1.0.Final > > > Steps to Reproduce: 1. add the lines in standalone.xml:- > {code} > <system-properties> > <property name="javax.net.ssl.trustStore" value="/dir/truststore.jks"/> > <property name="javax.net.ssl.trustStorePassword" value="${VAULT::blk::attr::MTBlYWUzNDEtMjI2MC00NWYzLWFiZmUtM2EyYjZkNDgyZWM4TElORV9CUkVBS215YWxpYXM=}" /> > </system-properties> > <vault> > <vault-option name="KEYSTORE_URL" value="/opt/jboss-eap-6.0/standalone/configuration/vault.jks"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-2gTQPnrWJaqrh0pURMKAOw"/> > <vault-option name="KEYSTORE_ALIAS" value="myalias"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="44"/> > <vault-option name="ENC_FILE_DIR" value="/opt/jboss-eap-6.0/standalone/configuration/"/> > </vault> > {code} > 2. start EAP6 in standalone mode > project_key: JBPAPP6 > Usage of vault for system-properties throws java.lang.SecurityException. > boot.log:- > {code} > 20:35:30,267 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([("system-property" => "javax.net.ssl.trustStorePassword")]): java.lang.SecurityException: JBAS013322: Vault is not initialized > at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:98) [jboss-as-security-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.RuntimeExpressionResolver.resolvePluggableExpression(RuntimeExpressionResolver.java:45) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressionsRecursively(ExpressionResolverImpl.java:58) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressions(ExpressionResolverImpl.java:40) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.resolveExpressions(ModelControllerImpl.java:455) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.OperationContextImpl.resolveExpressions(OperationContextImpl.java:689) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.operations.common.SystemPropertyAddHandler.execute(SystemPropertyAddHandler.java:112) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:175) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:191) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.ServerService.boot(ServerService.java:295) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_37] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-871: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1174871|https://bugzilla.redhat.com/show_bug.cgi?id=1174871] from ON_QA to VERIFIED > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_6_Final > > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Radim Vansa edited comment on JGRP-1876 at 1/12/15 8:01 AM: ------------------------------------------------------------ I was able to create a reproducer (SplitMergeTest.java, in attachment) on 4 nodes (actually trying to reproduce another issue). According to logs, each MergeView has two more subgroups. was (Author: rvansa): I was able to create a reproducer on 4 nodes (actually trying to reproduce another issue). According to logs, each MergeView has two more subgroups. > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1876: ------------------------------ Attachment: SplitMergeTest.java I was able to create a reproducer on 4 nodes (actually trying to reproduce another issue). According to logs, each MergeView has two more subgroups. > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-455) Include additional sun.jdk dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-455?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-455: ------------------------------------------------ Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 1172577|https://bugzilla.redhat.com/show_bug.cgi?id=1172577] from ON_QA to VERIFIED > Include additional sun.jdk dependencies > ---------------------------------------- > > Key: WFCORE-455 > URL: https://issues.jboss.org/browse/WFCORE-455 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 1.0.0.Alpha14 > Reporter: Mustafa Musaji > Assignee: David Lloyd > > Include the following out of the box for sun.jdk module > - for working with javax.sql.rowset.RowSetProvider > <path name="com/sun/rowset"/> > <path name="com/sun/rowset/providers"/> > - for working with java.lang.invoke.MethodHandleProxies > <path name="sun/invoke"/> > This affects EAP customers using CP releases when overlays override changes made in the original module.xml. For sun.jdk classes, the above packages should be included out of the box. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 January 2015