March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3605) Move the JMX subsystem out of core

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3605?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3605: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Move the JMX subsystem out of core > ---------------------------------- > > Key: WFLY-3605 > URL: https://issues.jboss.org/browse/WFLY-3605 > Project: WildFly > Issue Type: Task > Components: JMX > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Fix For: 9.0.0.CR1 > > > There are some dependency issues to resolve but the JMX subsystem should not automatically be included in the core distribution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3608) Expose configuring allowed file extensions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3608?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3608: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Expose configuring allowed file extensions > ------------------------------------------ > > Key: WFLY-3608 > URL: https://issues.jboss.org/browse/WFLY-3608 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: CentOs 5.5 & Ubuntu 10.04/12.04, Wildfly 8.1.0 Final, java version 1.7.0_60 > Reporter: Thomas Brenna > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > It should be possible to modify allowed extensions without adding web.xml entry as we have it now. > It should be an configuration option of servlet-container element. in undertow subsystem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3612) Implement missing transformers for new bean validation subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3612?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3612: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Implement missing transformers for new bean validation subsystem > ---------------------------------------------------------------- > > Key: WFLY-3612 > URL: https://issues.jboss.org/browse/WFLY-3612 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, EE > Reporter: Brian Stansberry > Assignee: Eduardo Martins > Fix For: 9.0.0.CR1 > > > The initial work on WFLY-3551 will be merged without needed transformers, because the transformer support we have won't allow the needed transformation. This JIRA is a reminder to add it once the required work in WFLY-3563 is done. > From my comment on the PR for the WFLY-3551 work: > There needs to be a discard of this resource if a legacy slave is involved. The presence of the resource means BV is wanted, and by default the legacy slave will have BV, so if this resource exists, the legacy slave is compatible. The resource just needs to be discarded so the legacy slave doesn't fail when it sees resources/ops for this subsystem it can't understand. > If this subsystem is omitted in a config with ee, the legacy slave will be out of sync with newer ones running the same profile, because the old ones will have BV and the new ones won't. But > 1) it's a corner case > 2) it may not matter anyway in terms of behavior of an app > 3) the transformer logic we have doesn't allow us to do anything about it anyway. > Re: that last part, when doing this work double check on skipping that, in case the WFLY-3563 work makes it real easy. Unlikely though. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3639) default-web-module doesn't work for non default host

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3639?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3639: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > default-web-module doesn't work for non default host > ---------------------------------------------------- > > Key: WFLY-3639 > URL: https://issues.jboss.org/browse/WFLY-3639 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > If you use config like this: > {code:xml} > <host name="default-host" default-web-module="myapp1.war" alias="webapp.domain1.com"/> > <host name="other-host" default-web-module="myapp2.war" alias="test.domain2.net"/> > {code} > and have apps myapp1.war & myapp2.war deployed myappwar2.war won't be bind to other-host. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3615) Clustering TS: mod_cluster integration test

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3615?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3615: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Clustering TS: mod_cluster integration test > ------------------------------------------- > > Key: WFLY-3615 > URL: https://issues.jboss.org/browse/WFLY-3615 > Project: WildFly > Issue Type: Task > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3659) wildfly 8 digest login-config throws javax.security.auth.callback.UnsupportedCallbackException

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3659?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3659: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > wildfly 8 digest login-config throws javax.security.auth.callback.UnsupportedCallbackException > ---------------------------------------------------------------------------------------------- > > Key: WFLY-3659 > URL: https://issues.jboss.org/browse/WFLY-3659 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Joseph Hwang > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > Password encryption in database login module with wildfly digest login config throws javax.security.auth.callback.UnsupportedCallbackException. These are sources. > == web.xml > <security-role> > <role-name>administrator</role-name> > </security-role> > <login-config> > <auth-method>DIGEST</auth-method> > <realm-name>WildFly8DigestRealm</realm-name> > </login-config> > == jboss-web.xml > <jboss-web> > <security-domain>java:/jaas/my_secure_domain</security-domain> > </jboss-web> > == standalone.xml > <security-domain name="my_secure_domain" cache-type="default"> > <authentication> > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/MySqlDS"/> > <module-option name="principalsQuery" value="select password from credential where uid=?"/> > <module-option name="rolesQuery" value="select urole, 'Roles' from credential where uid=?"/> > <module-option name="hashAlgorithm" value="MD5"/> > <module-option name="hashEncoding" value="RFC2617"/> > <module-option name="hashUserPassword" value="false"/> > <module-option name="hashStorePassword" value="true"/> > <module-option name="passwordIsA1Hash" value="true"/> > <module-option name="digestCallback" value="org.jboss.security.auth.callback.DigestCallbackHandler"/> > <module-option name="storeDigestCallback" value="org.jboss.security.auth.callback.RFC2617Digest"/> > </login-module> > </authentication> > </security-domain> > Password is encrypted with below codes > == EncryptPassword.java > package com.aaa.encrypt; > import org.jboss.crypto.CryptoUtil; > public class EncryptPassword { > public static void main(String[] args) { > // TODO Auto-generated method stub > String userName="admin"; > String realmName="WildFly8DigestRealm"; > String password="passwd123"; > String clearTextPassword=userName+":"+realmName+":"+password; > String hashedPassword=CryptoUtil.createPasswordHash("MD5", "RFC2617", null, null, clearTextPassword); > System.out.println("clearTextPassword: "+clearTextPassword); > System.out.println("hashedPassword: "+hashedPassword); > } > } > But login failed! The log shows the folowing exceptions : > 2014-07-18 21:37:45,246 TRACE [org.jboss.security] (default task-3) PBOX000236: Begin initialize method > 2014-07-18 21:37:45,246 DEBUG [org.jboss.security] (default task-3) PBOX000281: Password hashing activated, algorithm: MD5, encoding: RFC2617, charset: null, callback: org.jboss.security.auth.callback.DigestCallbackHandler, storeCallBack: org.jboss.security.auth.callback.RFC2617Digest > 2014-07-18 21:37:45,247 TRACE [org.jboss.security] (default task-3) PBOX000262: Module options [dsJndiName: java:jboss/datasources/MySqlDS, principalsQuery: select password from credential where uid=?, rolesQuery: select urole, 'Roles' from credential where uid=?, suspendResume: true] > 2014-07-18 21:37:45,247 TRACE [org.jboss.security] (default task-3) PBOX000240: Begin login method > 2014-07-18 21:37:45,249 TRACE [org.jboss.security] (default task-3) PBOX000263: Executing query select password from credential where uid=? with username admin > 2014-07-18 21:37:45,251 TRACE [org.jboss.security] (default task-3) PBOX000284: Created DigestCallback org.jboss.security.auth.callback.RFC2617Digest > 2014-07-18 21:37:45,252 TRACE [org.jboss.security] (default task-3) PBOX000244: Begin abort method > 2014-07-18 21:37:45,252 DEBUG [org.jboss.security] (default task-3) PBOX000206: Login failure: javax.security.auth.login.LoginException: PBOX000055: Failed to invoke CallbackHandler > at org.jboss.security.auth.spi.UsernamePasswordLoginModule.createPasswordHash(UsernamePasswordLoginModule.java:444) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1] > at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:280) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_60] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_60] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_60] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext.invoke(LoginContext.java:762) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext$4.run(LoginContext.java:690) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext$4.run(LoginContext.java:688) [rt.jar:1.7.0_60] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:687) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext.login(LoginContext.java:595) [rt.jar:1.7.0_60] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:408) [picketbox-infinispan-4.0.21.Beta1.jar:4.0.21.Beta1] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.21.Beta1.jar:4.0.21.Beta1] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:333) [picketbox-infinispan-4.0.21.Beta1.jar:4.0.21.Beta1] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146) [picketbox-infinispan-4.0.21.Beta1.jar:4.0.21.Beta1] > at org.wildfly.extension.undertow.security.JAASIdentityManagerImpl.verifyCredential(JAASIdentityManagerImpl.java:111) > at org.wildfly.extension.undertow.security.JAASIdentityManagerImpl.verify(JAASIdentityManagerImpl.java:77) > at io.undertow.security.impl.DigestAuthenticationMechanism.handleDigestHeader(DigestAuthenticationMechanism.java:265) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.DigestAuthenticationMechanism.authenticate(DigestAuthenticationMechanism.java:149) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:281) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:298) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:268) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:131) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:106) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:99) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:54) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:27) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:177) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] > Caused by: javax.security.auth.callback.UnsupportedCallbackException > at org.jboss.security.auth.callback.JBossCallbackHandler.handleCallBack(JBossCallbackHandler.java:138) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1] > at org.jboss.security.auth.callback.JBossCallbackHandler.handle(JBossCallbackHandler.java:87) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1] > at javax.security.auth.login.LoginContext$SecureCallbackHandler$1.run(LoginContext.java:947) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext$SecureCallbackHandler$1.run(LoginContext.java:944) [rt.jar:1.7.0_60] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_60] > at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:943) [rt.jar:1.7.0_60] > at org.jboss.security.auth.spi.UsernamePasswordLoginModule.createPasswordHash(UsernamePasswordLoginModule.java:434) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1] > ... 49 more > This cofiguration worked well in JBoss AS 7. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3679) Port jboss-as-infinispan_1_5.xsd schema from EAP to WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3679?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3679: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Port jboss-as-infinispan_1_5.xsd schema from EAP to WildFly > ----------------------------------------------------------- > > Key: WFLY-3679 > URL: https://issues.jboss.org/browse/WFLY-3679 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 9.0.0.CR1 > > > In addition to this the remaining infinispan schemas differ due to changes in the default values - these should be synchronized accordingly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3678) Port jboss-as-ee_1_2.xsd schema from EAP to WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3678?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3678: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Port jboss-as-ee_1_2.xsd schema from EAP to WildFly > --------------------------------------------------- > > Key: WFLY-3678 > URL: https://issues.jboss.org/browse/WFLY-3678 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Darran Lofthouse > Assignee: David Lloyd > Priority: Blocker > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3663) WildFly should manage JGroups and Infinispan thread pools by default

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3663?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3663: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > WildFly should manage JGroups and Infinispan thread pools by default > -------------------------------------------------------------------- > > Key: WFLY-3663 > URL: https://issues.jboss.org/browse/WFLY-3663 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > In our default configuration, both JGroups and Infinispan manage their own thread pools. Unfortunately, both projects do not handle thread pool lifecycle so well. Both projects use ExecutorService.shutdownNow() to end their thread pool lifecycles. This means that a channel or cache can stop, but still leave active threads running (albeit interrupted). We should have services that manage the lifecycle of our thread pools which ensure that all threads have terminated during Service.stop(). > This causes occasional OOMs in the Windows CI testsuite runs, due to too many threads lying around. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3805: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 9.0.0.CR1 > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 March 2015