October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6663) NPE o.j.a.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238)

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/WFLY-6663?page=com.atlassian.jira.plugin.... ] Darryl Miles commented on WFLY-6663: ------------------------------------ Just to report back some good news. I built wildfly 10.1.0.Final. Then cherry-pick this pull request patch. Then rebuilt. Then replaced wildfly-ejb3-10.1.0.Final.jar and I have not seen the issue I am reporting here occur. Thanks for patch. > NPE o.j.a.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238) > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-6663 > URL: https://issues.jboss.org/browse/WFLY-6663 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final, 10.1.0.Final > Environment: Win7 64bit + JDK8 64bit > Reporter: Darryl Miles > Assignee: Stuart Douglas > > 1 in 8 deployments fail to deploy, usually a redeploy fixes it. > If there is anyway to get a module state logging out of it, I can send over two logs to compare, one that deploy ok and one that fails. I guess there is a race bug there somewhere. > 09:42:01,687 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 529) MSC000001: Failed to start service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) > at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) > ... 6 more > Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb > at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83) > at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91) > at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106) > at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) > ... 11 more > Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb > at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:319) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:97) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103) > ... 26 more > Caused by: javax.naming.NamingException: WFLYNAM0062: Failed to lookup env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb [Root exception is java.lang.RuntimeException: WFLYEJB0423: Could not create session for stateful bean MainEjbImpl] > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:157) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:316) > ... 43 more > Caused by: java.lang.RuntimeException: WFLYEJB0423: Could not create session for stateful bean MainEjbImpl > at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:99) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143) > ... 48 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238) > at org.jboss.as.ejb3.remote.LocalEjbReceiver.openSession(LocalEjbReceiver.java:296) > at org.jboss.ejb.client.EJBClient.createSessionWithPossibleRetries(EJBClient.java:225) > at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:202) > at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:176) > at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:97) > ... 49 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1866) Make the authentication configurable in the eap testsuite

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1866?page=com.atlassian.jira.plugi... ] Filippe Spolti closed WFCORE-1866. ---------------------------------- Resolution: Done > Make the authentication configurable in the eap testsuite > --------------------------------------------------------- > > Key: WFCORE-1866 > URL: https://issues.jboss.org/browse/WFCORE-1866 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Priority: Optional > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1865) Make the authentication configurable in the eap testsuite

by Filippe Spolti (JIRA)

Filippe Spolti created WFCORE-1865: -------------------------------------- Summary: Make the authentication configurable in the eap testsuite Key: WFCORE-1865 URL: https://issues.jboss.org/browse/WFCORE-1865 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Reporter: Filippe Spolti Assignee: Filippe Spolti Priority: Optional -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1866) Make the authentication configurable in the eap testsuite

by Filippe Spolti (JIRA)

Filippe Spolti created WFCORE-1866: -------------------------------------- Summary: Make the authentication configurable in the eap testsuite Key: WFCORE-1866 URL: https://issues.jboss.org/browse/WFCORE-1866 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Reporter: Filippe Spolti Assignee: Filippe Spolti Priority: Optional -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml

by Adrian Boangiu (JIRA)

[ https://issues.jboss.org/browse/WFLY-7313?page=com.atlassian.jira.plugin.... ] Adrian Boangiu updated WFLY-7313: --------------------------------- Description: Without this feature it is impossible to migrate "variable" Java file permissions such as: permission java.io.FilePermission "${java.io.tmpdir}","read"; permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; that were defined in Java policy file in previous verions of JBoss. was: Without this feature it is impossible to migrate "variable" Java file permissions such as: permission java.io.FilePermission "${java.io.tmpdir}","read"; permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; that were defined in Java policy file up to the version J7 > Impossible to use environment variables or system properties in permissions.xml > ------------------------------------------------------------------------------- > > Key: WFLY-7313 > URL: https://issues.jboss.org/browse/WFLY-7313 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 10.1.0.Final > Reporter: Adrian Boangiu > Assignee: Jason Greene > Priority: Blocker > Fix For: 10.1.0.Final, 10.2.0.Final > > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml

by Adrian Boangiu (JIRA)

[ https://issues.jboss.org/browse/WFLY-7313?page=com.atlassian.jira.plugin.... ] Adrian Boangiu updated WFLY-7313: --------------------------------- Description: Without this feature it is impossible to migrate "variable" Java file permissions such as: permission java.io.FilePermission "${java.io.tmpdir}","read"; permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; that were defined in Java policy file up to the version J7 > Impossible to use environment variables or system properties in permissions.xml > ------------------------------------------------------------------------------- > > Key: WFLY-7313 > URL: https://issues.jboss.org/browse/WFLY-7313 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 10.1.0.Final > Reporter: Adrian Boangiu > Assignee: Jason Greene > Priority: Blocker > Fix For: 10.1.0.Final, 10.2.0.Final > > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > that were defined in Java policy file up to the version J7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Jiri Locker commented on DROOLS-1326: ------------------------------------- [~ge0ffrey], I can't reproduce locally with current master. I invoke {noformat} mvn test -DrunTurtleTests -Dtest=NurseRosteringSolveAllTurtleTest {noformat} I also checked out commits from the date when the failed Jenkins build was launched and it didn't help. I suggest re-running the job. If it fails again, either I or the job does something wrong. Any other ideas? > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml

by Adrian Boangiu (JIRA)

Adrian Boangiu created WFLY-7313: ------------------------------------ Summary: Impossible to use environment variables or system properties in permissions.xml Key: WFLY-7313 URL: https://issues.jboss.org/browse/WFLY-7313 Project: WildFly Issue Type: Feature Request Affects Versions: 10.1.0.Final Reporter: Adrian Boangiu Assignee: Jason Greene Priority: Blocker Fix For: 10.2.0.Final, 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1330) Events already expired at insertion time don't have a chance to produce a match

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1330: ----------------------------------- Summary: Events already expired at insertion time don't have a chance to produce a match Key: DROOLS-1330 URL: https://issues.jboss.org/browse/DROOLS-1330 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco When flushing the insertion of an event that is already expired at processing (firing) time it is required that the event should however have at least a chance to produce joins and activations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1329) Events already expired at insertion time don't have a chance to produce a match

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1329: ----------------------------------- Summary: Events already expired at insertion time don't have a chance to produce a match Key: DROOLS-1329 URL: https://issues.jboss.org/browse/DROOLS-1329 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco When flushing the insertion of an event that is already expired at processing (firing) time it is required that the event should however have at least a chance to produce joins and activations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 October 2016