February 2014 - jboss-jira - Jboss List Archives

[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: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017881|https://bugzilla.redhat.com/show_bug.cgi?id=1017881] from MODIFIED to ON_QA > 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 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2660) LDAP Group Loading - Should Not Fail for Non-existent User.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2660?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2660: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1043667|https://bugzilla.redhat.com/show_bug.cgi?id=1043667] from MODIFIED to ON_QA > LDAP Group Loading - Should Not Fail for Non-existent User. > ----------------------------------------------------------- > > Key: WFLY-2660 > URL: https://issues.jboss.org/browse/WFLY-2660 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Final > > > Where a security realm is configured to load groups from LDAP it should not cause an authentication failure if the user is not found in LDAP. > One example is local authentication where the user may not exist. > Another is domain mode servers where the servers have a custom name and generated password that they use to connect back to the local host controller. -- 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, 4 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: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 924562|https://bugzilla.redhat.com/show_bug.cgi?id=924562] from MODIFIED to ON_QA > 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 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2595) Logging DUP leaking class loaders

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2595?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2595: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1038305|https://bugzilla.redhat.com/show_bug.cgi?id=1038305] from MODIFIED to ON_QA > Logging DUP leaking class loaders > --------------------------------- > > Key: WFLY-2595 > URL: https://issues.jboss.org/browse/WFLY-2595 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 8.0.0.CR1 > > > When a new {{LogContext}} is created for per-deployment logging the class loader is registered as the key. On undeploy the {{LogContext}} should be removed, but the wrong {{LogContext}}t is retrieved due to the caller class loader being used rather than the TCCL. > The use of the caller class loader is for filtering out system dependencies from the deployment so the correct {{LogContext}} is retrieved from the selector. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1594) Domain Management logout 'feature' not working for HTTP BASIC authentication.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1594?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1594: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 976917|https://bugzilla.redhat.com/show_bug.cgi?id=976917] from MODIFIED to ON_QA > Domain Management logout 'feature' not working for HTTP BASIC authentication. > ----------------------------------------------------------------------------- > > Key: WFLY-1594 > URL: https://issues.jboss.org/browse/WFLY-1594 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > > The logout capability assumes Digest authentication, where we have used LDAP for authentication we only use BASIC authentication. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2161) JBAS014356 exception not thrown for @Asyncronous EJB methods

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2161?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2161: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1060734|https://bugzilla.redhat.com/show_bug.cgi?id=1060734] from MODIFIED to ON_QA > JBAS014356 exception not thrown for @Asyncronous EJB methods > ------------------------------------------------------------ > > Key: WFLY-2161 > URL: https://issues.jboss.org/browse/WFLY-2161 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Alpha4 > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > If you call an ejb method with default visibility (e.g. from a servlet in the same package), an EJBException with code JBAS014356 is thrown because the method is not public. > If the method is annotated with @Asynchronous and returns void, the exception is not seen because the interceptor from AsyncFutureInterceptorFactory is used before NotBusinessMethodInterceptor, the exception is thrown in the worker thread instead. > With a void return, the exception is silently dropped. With a Future<?> return, it will be set as the failure exception on the future rather than being thrown from the call. > As per the forum reference we need to check the spec, but the validity of the business method should probably be checked before the handoff to the worker thread. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2696) management audit settings: syslog protocol is lowercase while uppercase is expected

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2696?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2696: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1047519|https://bugzilla.redhat.com/show_bug.cgi?id=1047519] from MODIFIED to ON_QA > management audit settings: syslog protocol is lowercase while uppercase is expected > ----------------------------------------------------------------------------------- > > Key: WFLY-2696 > URL: https://issues.jboss.org/browse/WFLY-2696 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Environment: - 8.0.0 CR1 + latest code in master > - domain mode > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > Fix For: 8.0.0.Final > > > Add a syslog handler to the audit settings of the management service of the domain controller, then start an instance. It fails to start with: > JBAS014612: Operation ("register-server") failed - address: ([]): java.lang.IllegalArgumentException: No enum const class org.jboss.as.controller.audit.SyslogAuditLogHandler$Transport.udp > at java.lang.Enum.valueOf(Enum.java:214) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2370) NPE in DelegatingServerInventory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2370?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2370: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1024109|https://bugzilla.redhat.com/show_bug.cgi?id=1024109] from MODIFIED to ON_QA > NPE in DelegatingServerInventory > -------------------------------- > > Key: WFLY-2370 > URL: https://issues.jboss.org/browse/WFLY-2370 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=4738&tab=build... > Test failure: > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.domain.DomainControllerMigrationTestCase.testDCFailover(DomainControllerMigrationTestCase.java:223) > This appears in the log: > [Host Controller] 03:26:38,028 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014612: Operation ("read-attribute") failed - address: ([ > [Host Controller] ("host" => "failover-h1"), > [Host Controller] ("server-config" => "failover-one") > [Host Controller] ]): java.lang.NullPointerException > [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.determineServerStatus(DomainModelControllerService.java:788) > [Host Controller] at org.jboss.as.host.controller.operations.ServerStatusHandler.execute(ServerStatusHandler.java:66) > [Host Controller] at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:177) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:97) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:151) [wildfly-controller-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] -- 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, 4 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: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1055740|https://bugzilla.redhat.com/show_bug.cgi?id=1055740] from MODIFIED to ON_QA > 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 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2319) LDAP Search containing URL - InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2319?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2319: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1060275|https://bugzilla.redhat.com/show_bug.cgi?id=1060275] from MODIFIED to ON_QA > LDAP Search containing URL - InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-2319 > URL: https://issues.jboss.org/browse/WFLY-2319 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Eduardo Martins > Fix For: 8.0.0.Final > > Attachments: LdapSearching.tgz > > > The following code: - > {code} > Hashtable env = new Hashtable(); > env.put("java.naming.factory.initial", "com.sun.jndi.ldap.LdapCtxFactory"); > env.put("java.naming.security.authentication", "simple"); > env.put("java.naming.provider.url", "ldap://localhost:10389"); > env.put(InitialDirContext.SECURITY_PRINCIPAL, "uid=admin,ou=system"); > env.put(InitialDirContext.SECURITY_CREDENTIALS, "secret"); > SearchControls ctl = null; > String attrArr[] = new String[1]; > attrArr[0] = "sn"; > ctl = new SearchControls(2, 0L, 0, attrArr, false, false); > String base = "ldap://localhost:10389/dc=simple,dc=wildfly,dc=org"; > String filter = "(uid=UserOne)"; > NamingEnumeration nenum = null; > DirContext ictx = null; > ictx = new InitialDirContext(env); > nenum = ictx.search(base, filter, ctl); > {code} > Results in the following exception: - > {noquote} > 13:03:45,598 ERROR [stderr] (default task-1) javax.naming.InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given : ldap: (0x6C 0x64 0x61 0x70 0x3A ) is invalid]; remaining name 'ldap://localhost:10389/dc=simple,dc=wildfly,dc=org' > 13:03:45,599 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3025) > 13:03:45,600 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840) > 13:03:45,600 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1034) > {noquote} > Switching to a base that does not begin with a URL and the search works, executing this code outside of WildFly also works. > The underlying issue is that the default InitialContext implementation contains the following method: - > {code} > protected Context getURLOrDefaultInitCtx(String name) > throws NamingException { > if (NamingManager.hasInitialContextFactoryBuilder()) { > return getDefaultInitCtx(); > } > String scheme = getURLScheme(name); > if (scheme != null) { > Context ctx = NamingManager.getURLContext(scheme, myProps); > if (ctx != null) { > return ctx; > } > } > return getDefaultInitCtx(); > } > {code} > As the naming subsystem has registered a InitialContextFactoryBuilder this code will never fall down to the scheme specific section. -- 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, 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 February 2014