December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2614) NPE Defining security realm with empty keystore alias

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2614?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-2614: -------------------------------------- Assignee: Darran Lofthouse > NPE Defining security realm with empty keystore alias > ----------------------------------------------------- > > Key: WFLY-2614 > URL: https://issues.jboss.org/browse/WFLY-2614 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > > The following is logged if alias="" > {noformat} > Caused by: java.lang.NullPointerException: invalid null input > at java.security.KeyStore.setEntry(KeyStore.java:1321) [rt.jar:1.7.0_13] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:106) > at org.jboss.as.domain.management.security.FileKeystoreService.start(FileKeystoreService.java:60) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > ... 3 more > {noformat} > An alias of a zero length string should be rejected in the config and model. It never worked so not a backwards compatibility issue. > The alias should also be checked against the keystore and an appropriate error reported if not present. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2614) NPE Defining security realm with empty keystore alias

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2614?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2614: ----------------------------------- Affects Version/s: 8.0.0.Beta1 > NPE Defining security realm with empty keystore alias > ----------------------------------------------------- > > Key: WFLY-2614 > URL: https://issues.jboss.org/browse/WFLY-2614 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > > The following is logged if alias="" > {noformat} > Caused by: java.lang.NullPointerException: invalid null input > at java.security.KeyStore.setEntry(KeyStore.java:1321) [rt.jar:1.7.0_13] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:106) > at org.jboss.as.domain.management.security.FileKeystoreService.start(FileKeystoreService.java:60) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > ... 3 more > {noformat} > An alias of a zero length string should be rejected in the config and model. It never worked so not a backwards compatibility issue. > The alias should also be checked against the keystore and an appropriate error reported if not present. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2614) NPE Defining security realm with empty keystore alias

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2614?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2614: ----------------------------------- Component/s: Domain Management > NPE Defining security realm with empty keystore alias > ----------------------------------------------------- > > Key: WFLY-2614 > URL: https://issues.jboss.org/browse/WFLY-2614 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > > The following is logged if alias="" > {noformat} > Caused by: java.lang.NullPointerException: invalid null input > at java.security.KeyStore.setEntry(KeyStore.java:1321) [rt.jar:1.7.0_13] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:106) > at org.jboss.as.domain.management.security.FileKeystoreService.start(FileKeystoreService.java:60) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > ... 3 more > {noformat} > An alias of a zero length string should be rejected in the config and model. It never worked so not a backwards compatibility issue. > The alias should also be checked against the keystore and an appropriate error reported if not present. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2614) NPE Defining security realm with empty keystore alias

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2614?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2614: ----------------------------------- Fix Version/s: 8.0.0.CR1 > NPE Defining security realm with empty keystore alias > ----------------------------------------------------- > > Key: WFLY-2614 > URL: https://issues.jboss.org/browse/WFLY-2614 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > The following is logged if alias="" > {noformat} > Caused by: java.lang.NullPointerException: invalid null input > at java.security.KeyStore.setEntry(KeyStore.java:1321) [rt.jar:1.7.0_13] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:106) > at org.jboss.as.domain.management.security.FileKeystoreService.start(FileKeystoreService.java:60) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > ... 3 more > {noformat} > An alias of a zero length string should be rejected in the config and model. It never worked so not a backwards compatibility issue. > The alias should also be checked against the keystore and an appropriate error reported if not present. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1123) ManagedConnectionPoolStatistics not correctly enabled at init

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1123?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1123. ------------------------------------ Resolution: Done > ManagedConnectionPoolStatistics not correctly enabled at init > ------------------------------------------------------------- > > Key: JBJCA-1123 > URL: https://issues.jboss.org/browse/JBJCA-1123 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.23.Final, 1.1.2.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.24.Final, 1.1.3.Final > > > ManagedConnectionPoolStatistics needs to be initialized with PoolStatistics' enabled status -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2611) Support CDI injection in various JSF artifacts

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/WFLY-2611?page=com.atlassian.jira.plugin.... ] Tomas Remes updated WFLY-2611: ------------------------------ Description: If I understand correctly to the subchapter "5.4.1 JSF Managed Classes and Java EE Annotations" of JSF 2.2 specification, there should be opportunity to use a lot of (and not only) CDI annotations in various JSF artifacts (ActionListener, SystemEventListener, etc. - for full list, please see the spec). So far I tried locally this (will be filling the table during time): ||JSF artifact||CDI Injection|| |javax.el.ELResolver|| |javax.faces.application.ApplicationFactory|| |javax.faces.application.NavigationHandler|| |javax.faces.application.ResourceHandler|| |javax.faces.application.StateManager|works (however there is question about availability of injected instances in constructor of this custom delegating object| |javax.faces.component.visit.VisitContextFactory||| |javax.faces.context.ExceptionHandlerFactory||| |javax.faces.context.ExternalContextFactory||| |javax.faces.context.FacesContextFactory|works| |javax.faces.context.PartialViewContextFactory|| |javax.faces.event.ActionListener|works only when specified also in faces-config| |javax.faces.event.SystemEventListener|doesn't work| |javax.faces.lifecycle.ClientWindowFactory|| |javax.faces.lifecycle.LifecycleFactory|| |javax.faces.lifecycle.PhaseListener|works| |javax.faces.render.RenderKitFactory|| |javax.faces.view.ViewDeclarationFactory|| |javax.faces.view.facelets.FaceletCacheFactory|| |javax.faces.view.facelets.FaceletFactory|| |javax.faces.view.facelets.TagHandlerDelegateFactory|| was: If I understand correctly to the subchapter "5.4.1 JSF Managed Classes and Java EE Annotations" of JSF 2.2 specification, there should be opportunity to use a lot of (and not only) CDI annotations in various JSF artifacts (ActionListener, SystemEventListener, etc. - for full list, please see the spec). So far I tried locally this (will be filling the table during time): ||JSF artifact||CDI Injection|| |javax.el.ELResolver|| |javax.faces.application.ApplicationFactory|| |javax.faces.application.NavigationHandler|| |javax.faces.application.ResourceHandler|| |javax.faces.application.StateManager||| |javax.faces.component.visit.VisitContextFactory||| |javax.faces.context.ExceptionHandlerFactory||| |javax.faces.context.ExternalContextFactory||| |javax.faces.context.FacesContextFactory|works| |javax.faces.context.PartialViewContextFactory|| |javax.faces.event.ActionListener|works only when specified also in faces-config| |javax.faces.event.SystemEventListener|doesn't work| |javax.faces.lifecycle.ClientWindowFactory|| |javax.faces.lifecycle.LifecycleFactory|| |javax.faces.lifecycle.PhaseListener|works| |javax.faces.render.RenderKitFactory|| |javax.faces.view.ViewDeclarationFactory|| |javax.faces.view.facelets.FaceletCacheFactory|| |javax.faces.view.facelets.FaceletFactory|| |javax.faces.view.facelets.TagHandlerDelegateFactory|| > Support CDI injection in various JSF artifacts > ---------------------------------------------- > > Key: WFLY-2611 > URL: https://issues.jboss.org/browse/WFLY-2611 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: CDI / Weld > Reporter: Tomas Remes > Assignee: Stuart Douglas > > If I understand correctly to the subchapter "5.4.1 > JSF Managed Classes and Java EE Annotations" of JSF 2.2 specification, there should be opportunity to use a lot of (and not only) CDI annotations in various JSF artifacts (ActionListener, SystemEventListener, etc. - for full list, please see the spec). > So far I tried locally this (will be filling the table during time): > ||JSF artifact||CDI Injection|| > |javax.el.ELResolver|| > |javax.faces.application.ApplicationFactory|| > |javax.faces.application.NavigationHandler|| > |javax.faces.application.ResourceHandler|| > |javax.faces.application.StateManager|works (however there is question about availability of injected instances in constructor of this custom delegating object| > |javax.faces.component.visit.VisitContextFactory||| > |javax.faces.context.ExceptionHandlerFactory||| > |javax.faces.context.ExternalContextFactory||| > |javax.faces.context.FacesContextFactory|works| > |javax.faces.context.PartialViewContextFactory|| > |javax.faces.event.ActionListener|works only when specified also in faces-config| > |javax.faces.event.SystemEventListener|doesn't work| > |javax.faces.lifecycle.ClientWindowFactory|| > |javax.faces.lifecycle.LifecycleFactory|| > |javax.faces.lifecycle.PhaseListener|works| > |javax.faces.render.RenderKitFactory|| > |javax.faces.view.ViewDeclarationFactory|| > |javax.faces.view.facelets.FaceletCacheFactory|| > |javax.faces.view.facelets.FaceletFactory|| > |javax.faces.view.facelets.TagHandlerDelegateFactory|| > -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-17) ignore CNFE when scanning for entity classes in deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-17?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-17: --------------------------------------------- Zbyněk Roubalík <zroubali(a)redhat.com> changed the Status of [bug 1006617|https://bugzilla.redhat.com/show_bug.cgi?id=1006617] from ON_QA to VERIFIED > ignore CNFE when scanning for entity classes in deployment > ---------------------------------------------------------- > > Key: WFLY-17 > URL: https://issues.jboss.org/browse/WFLY-17 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: cnfe.jar > > > Deployments may contain non-entity classes that can not be loaded (see above forum reference for example). -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2364) Uninformative NPE in PoolAnnotationInformationFactory

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-2364?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on WFLY-2364: ---------------------------------------- Stuart Douglas merged the patch into wildfly master. Resolving. > Uninformative NPE in PoolAnnotationInformationFactory > ------------------------------------------------------ > > Key: WFLY-2364 > URL: https://issues.jboss.org/browse/WFLY-2364 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Denis Borovikov > Assignee: David Lloyd > > I got NPE on jboss startup: > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.deployment.processors.annotation.PoolAnnotationInformationFactory.fromAnnotation(PoolAnnotationInformationFactory.java:43) > at org.jboss.as.ejb3.deployment.processors.annotation.PoolAnnotationInformationFactory.fromAnnotation(PoolAnnotationInformationFactory.java:35) > at org.jboss.as.ee.metadata.ClassAnnotationInformationFactory.createAnnotationInformation(ClassAnnotationInformationFactory.java:127) > at org.jboss.as.ee.metadata.AbstractEEAnnotationProcessor.deploy(AbstractEEAnnotationProcessor.java:54) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > ... 5 more > Root cause is empty value for Pool annotation in my code. I think it would be better to generate more informative exception message in this place. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1921) Cancel operation is ignored when flushing JMS destination metrics in the management console

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-1921?page=com.atlassian.jira.plugin.... ] Harald Pehl resolved WFLY-1921. ------------------------------- Resolution: Done Fixed in upstream. Will be part of WF 8 and EAP 6.2.CP0a. > Cancel operation is ignored when flushing JMS destination metrics in the management console > ------------------------------------------------------------------------------------------- > > Key: WFLY-1921 > URL: https://issues.jboss.org/browse/WFLY-1921 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Osamu Nagano > Assignee: Harald Pehl > > When you push "Flush" button on JMS Destinations runtime tab (both of queues and topics), a confirmation dialog box brings up. "Cancel" button in the dialog box is always ignored and destination flushing is inevitably executed. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1921) Cancel operation is ignored when flushing JMS destination metrics in the management console

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-1921?page=com.atlassian.jira.plugin.... ] Harald Pehl reassigned WFLY-1921: --------------------------------- Assignee: Harald Pehl (was: Heiko Braun) > Cancel operation is ignored when flushing JMS destination metrics in the management console > ------------------------------------------------------------------------------------------- > > Key: WFLY-1921 > URL: https://issues.jboss.org/browse/WFLY-1921 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Osamu Nagano > Assignee: Harald Pehl > > When you push "Flush" button on JMS Destinations runtime tab (both of queues and topics), a confirmation dialog box brings up. "Cancel" button in the dialog box is always ignored and destination flushing is inevitably executed. -- 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

10 years, 7 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 December 2013