June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2214: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1015303|https://bugzilla.redhat.com/show_bug.cgi?id=1015303] from VERIFIED to CLOSED > Allow additional environment properties to be set for outbound LDAP connections used by security realms. > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2214 > URL: https://issues.jboss.org/browse/WFLY-2214 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > LDAP security realm needs to have configurable timeouts. > The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy. > The following hack appears to work: > +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java > @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag > result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory); > String url = config.require(URL).asString(); > result.put(Context.PROVIDER_URL,url); > + result.put("com.sun.jndi.ldap.connect.timeout", "500"); > return result; > } -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2725) Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2725?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2725: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1049999|https://bugzilla.redhat.com/show_bug.cgi?id=1049999] from VERIFIED to CLOSED > Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module > -------------------------------------------------------------------------------------------------- > > Key: WFLY-2725 > URL: https://issues.jboss.org/browse/WFLY-2725 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.CR1 > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: 8.0.0.Final > > > 'JBAS011046: A component named > 'TestBean' is already defined in this module', I have narrowed it > down to it occurs if they have a jar manifest with Class-Path: . > It looks like when deploying it looks at the jar with the manifest > entry which then must be having it scan the jar containing the EJB > again and failing. > Having the Class-Path: . doesn't really make sense to me, however it > also seems like we should not be trying to deploy it twice. > It appears ManifestClassPathProcessor ignores the . when the Class-Path is in a jar at the root of an ear but not when the jar is in a war's WEB-INF/lib > server/src/main/java/org/jboss/as/server/deployment/module/ManifestClassPathProcessor.java -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-975) Deployment replace causes invalid state in DUP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-975?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-975: ---------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 924562|https://bugzilla.redhat.com/show_bug.cgi?id=924562] from VERIFIED to CLOSED > Deployment replace causes invalid state in DUP > ---------------------------------------------- > > Key: WFLY-975 > URL: https://issues.jboss.org/browse/WFLY-975 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Reporter: Thomas Diesler > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > Attachments: v200.jar, v201.jar, webapp-v200.war > > > Webapp A depends on deployment B. Replacing B causes NPE in JPAInterceptorProcessor > {code} > 12:52:05,712 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "v200.jar" (runtime-name: "v200.jar") > 12:52:05,889 INFO [org.jboss.as.server] (XNIO-1 task-8) JBAS018559: Deployed "v200.jar" (runtime-name : "v200.jar") > 12:52:37,207 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "webapp-v200.war" (runtime-name: "webapp-v200.war") > 12:52:37,349 INFO [org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register web context: /webapp-v200 > 12:52:37,436 INFO [org.jboss.as.server] (XNIO-1 task-3) JBAS018559: Deployed "webapp-v200.war" (runtime-name : "webapp-v200.war") > 12:53:20,252 INFO [org.jboss.web] (ServerService Thread Pool -- 57) JBAS018224: Unregister web context: /webapp-v200 > 12:53:20,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment v200.jar (runtime-name: v200.jar) in 25ms > 12:53:20,274 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "v200.jar" (runtime-name: "v200.jar") > 12:53:20,293 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."webapp-v200.war".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webapp-v200.war".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "webapp-v200.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1972) [jboss-msc-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1905) [jboss-msc-1.1.1.Final.jar:1.1.1.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.NullPointerException > at org.jboss.as.jpa.processor.JPAInterceptorProcessor.deploy(JPAInterceptorProcessor.java:52) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > ... 5 more > {code} > What might be happening here is that replacing B causes ModuleB to go down. Phase FIRST_MODULE_USE of A depends on ModuleB, which causes a call to undeploy() on the DUPs for A. When ModuleB becomes available again, deploy() is called on the DUPs for A again. Possibly because of the cleanup phase, necessary state is lost and we see a NPE. > AFAICS, this is a variation of the feature request that DUPs support multiple calls to deploy/undeploy. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3283) Upgrade Generic JMS RA to 1.0.5.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3283: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1090961|https://bugzilla.redhat.com/show_bug.cgi?id=1090961] from VERIFIED to CLOSED > Upgrade Generic JMS RA to 1.0.5.Final > ------------------------------------- > > Key: WFLY-3283 > URL: https://issues.jboss.org/browse/WFLY-3283 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.1.0.CR1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.1.0.CR2, 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2849) Upgrade jboss-remote-naming to 2.0.0 Final or later

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2849?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2849: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1024153|https://bugzilla.redhat.com/show_bug.cgi?id=1024153] from VERIFIED to CLOSED > Upgrade jboss-remote-naming to 2.0.0 Final or later > --------------------------------------------------- > > Key: WFLY-2849 > URL: https://issues.jboss.org/browse/WFLY-2849 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.CR1 > Reporter: Brad Maxwell > Assignee: Eduardo Martins > > Upgrade jboss-remote-naming to 2.0.0 Final or later to resolve linked issues -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2782) Testsuite leaks remoting endpoints by not closing JMXConnector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2782?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2782: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1055740|https://bugzilla.redhat.com/show_bug.cgi?id=1055740] from VERIFIED to CLOSED > Testsuite leaks remoting endpoints by not closing JMXConnector > -------------------------------------------------------------- > > Key: WFLY-2782 > URL: https://issues.jboss.org/browse/WFLY-2782 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Final > > > Whereever JMXConnectorFactory.connect() is called, the resulting JMXConnector should be closed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-805: -------------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1079930|https://bugzilla.redhat.com/show_bug.cgi?id=1079930] from VERIFIED to CLOSED > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: PicketBox_4_0_21.Beta2, PicketBox_4_0_19.SP5 > > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1712) Erroneous name attribute on root-logger after add-handler operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1712: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1017881|https://bugzilla.redhat.com/show_bug.cgi?id=1017881] from VERIFIED to CLOSED > Erroneous name attribute on root-logger after add-handler operation > -------------------------------------------------------------------- > > Key: WFLY-1712 > URL: https://issues.jboss.org/browse/WFLY-1712 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Execution of the {{add-handler}} operation adds a name attribute with the handlers name to the root-logger model. > {code} > "root-logger" => {"ROOT" => { > "filter" => undefined, > "filter-spec" => undefined, > "handlers" => [ > "FILE", > "CONSOLE" > ], > "level" => "INFO", > "name" => "CONSOLE" > }} > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3392) Make the test suite more robust for DomainDeployWithRuntimeNameTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3392?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3392: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1100223|https://bugzilla.redhat.com/show_bug.cgi?id=1100223] from VERIFIED to CLOSED > Make the test suite more robust for DomainDeployWithRuntimeNameTestCase > ----------------------------------------------------------------------- > > Key: WFLY-3392 > URL: https://issues.jboss.org/browse/WFLY-3392 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR2 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Trivial > Fix For: 9.0.0.Alpha1 > > > The test DomainDeployWithRuntimeNameTestCase depends on the server groups list which is backed by a Set. > Converting it to a list ands osrting it makes the test more reliable -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2303) mod_cluster XSD is missing property and worker-timeout definitions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2303?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2303: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1020142|https://bugzilla.redhat.com/show_bug.cgi?id=1020142] from VERIFIED to CLOSED > mod_cluster XSD is missing property and worker-timeout definitions > ------------------------------------------------------------------ > > Key: WFLY-2303 > URL: https://issues.jboss.org/browse/WFLY-2303 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > * worker-timeout > * property > are missing. > Also missing in 7.x -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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