November 2013 - jboss-jira - Jboss List Archives

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

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/WFLY-2364?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere updated WFLY-2364: -------------------------------------- Component/s: EJB > 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 > > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Kabir Khan edited comment on WFLY-2589 at 11/29/13 7:40 AM: ------------------------------------------------------------ In real life, on the DC the defaults are not passed in. For the comparison in the tests, the defaults are nice in a way. Still, we should probably work with what is correct. was (Author: kabirkhan): In domain mode the defaults are not passed in. For the comparison in the tests, the defaults are nice in a way. Still, we should probably work with what is correct. > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-358) KieModule resulting from an incremental compilation cannot be used to update a KieContainer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-358: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1036096|https://bugzilla.redhat.com/show_bug.cgi?id=1036096] from NEW to ASSIGNED > KieModule resulting from an incremental compilation cannot be used to update a KieContainer > ------------------------------------------------------------------------------------------- > > Key: DROOLS-358 > URL: https://issues.jboss.org/browse/DROOLS-358 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > > Programmatic incremental compilation modifies the existing KieModule in place instead of creating a new one. This makes impossible to upgrade a KieContainer with the kieModulre resulting from the incremental compilation. In fact in this case the new KieModule is identical (same instance) to the old one making the automatic KieModule comparison useless. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-358) KieModule resulting from an incremental compilation cannot be used to update a KieContainer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-358: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1036096 > KieModule resulting from an incremental compilation cannot be used to update a KieContainer > ------------------------------------------------------------------------------------------- > > Key: DROOLS-358 > URL: https://issues.jboss.org/browse/DROOLS-358 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > > Programmatic incremental compilation modifies the existing KieModule in place instead of creating a new one. This makes impossible to upgrade a KieContainer with the kieModulre resulting from the incremental compilation. In fact in this case the new KieModule is identical (same instance) to the old one making the automatic KieModule comparison useless. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-358) KieModule resulting from an incremental compilation cannot be used to update a KieContainer

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-358: ---------------------------------- Summary: KieModule resulting from an incremental compilation cannot be used to update a KieContainer Key: DROOLS-358 URL: https://issues.jboss.org/browse/DROOLS-358 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Programmatic incremental compilation modifies the existing KieModule in place instead of creating a new one. This makes impossible to upgrade a KieContainer with the kieModulre resulting from the incremental compilation. In fact in this case the new KieModule is identical (same instance) to the old one making the automatic KieModule comparison useless. -- 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, 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: ---------------------------------------- as for org.jboss.ejb3.annotation.Pool value is required. I thus added a check that would throw an appropriate exception if it's missing. > 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) > Reporter: Denis Borovikov > > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-770) Support external password for keystore of PicketBoxVault implementation

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-770?page=com.atlassian.jira.plug... ] Ivo Studensky updated SECURITY-770: ----------------------------------- Attachment: (was: SECURITY-770.patch) > Support external password for keystore of PicketBoxVault implementation > ----------------------------------------------------------------------- > > Key: SECURITY-770 > URL: https://issues.jboss.org/browse/SECURITY-770 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_19.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Attachments: SECURITY-770_with_testcase.patch > > > At the moment, the default implementation of Vault supports masked keystore password only. It would be nice to add a facility for external keystore password too so that customers can either define an external command to get the password or define their own class which provides a password for the keystore. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-770) Support external password for keystore of PicketBoxVault implementation

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-770?page=com.atlassian.jira.plug... ] Ivo Studensky updated SECURITY-770: ----------------------------------- Attachment: SECURITY-770_with_testcase.patch Updated the patch with new test-cases. > Support external password for keystore of PicketBoxVault implementation > ----------------------------------------------------------------------- > > Key: SECURITY-770 > URL: https://issues.jboss.org/browse/SECURITY-770 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_19.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Attachments: SECURITY-770_with_testcase.patch > > > At the moment, the default implementation of Vault supports masked keystore password only. It would be nice to add a facility for external keystore password too so that customers can either define an external command to get the password or define their own class which provides a password for the keystore. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-357) Multiple static initialization makes debugging Maven issues impossible

by Lukáš Petrovický (JIRA)

Lukáš Petrovický created DROOLS-357: --------------------------------------- Summary: Multiple static initialization makes debugging Maven issues impossible Key: DROOLS-357 URL: https://issues.jboss.org/browse/DROOLS-357 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Lukáš Petrovický Assignee: Mario Fusco When running kie-ci tests against productized binaries, most of the tests in that module fail with this particular exception (or similar): java.lang.NoClassDefFoundError: Could not initialize class org.kie.scanner.MavenRepository at org.kie.scanner.KieModuleMavenTest.testKieModulePojoDependencies(KieModuleMavenTest.java:119) Turns out, this exception is (through multiple levels of static initialization) actually caused here: https://github.com/droolsjbpm/drools/blob/master/kie-ci/src/main/java/org... Maven resolution fails, because it cannot find some dependencies in the project being loaded. As a result, the class is never initialized, fast forward two other classes, and you get the above exception. I kindly ask that this behavior be changed in such a way that the original exception bubbles up through the stack - otherwise, the user has no chance to figure out what's going on. The issue is a bit tricky to reproduce, as it's directly related to artifacts not being resolvable - but it should, if my understanding of the error is correct, be enough to have a parser error in the POM that's being loaded. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1085) No audit feature for security-realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1085?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1085: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 912233|https://bugzilla.redhat.com/show_bug.cgi?id=912233] from ON_QA to ASSIGNED > No audit feature for security-realm > ----------------------------------- > > Key: WFLY-1085 > URL: https://issues.jboss.org/browse/WFLY-1085 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Logging > Environment: EAP 6.0.x > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > There is no auditing feature for security-realm. Need the feature like audit provider for security-domain. -- 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, 7 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 November 2013