[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf updated EJBTHREE-2155: ------------------------------------ Attachment: threads_report.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf updated EJBTHREE-2155: ------------------------------------ Component Fix Version(s): (was: core-1.3.6, metrics-deployer-1.1.0) Component/s: (was: metrics-deployer) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf updated EJBTHREE-2155: ------------------------------------ Fix Version/s: (was: depchain-1.0.0) (was: bom-eap5-1.0.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf commented on EJBTHREE-2155: ----------------------------------------- await in the testThreeThreads returns 2 (so it was the first to arrive) 14:31:20,122 DEBUG [NoopBean] entering barriers 14:31:20,122 DEBUG [NoopBean] entering barriers 2 While the other 2 threads have 'count = 3' in the CyclicBarrier. Why is CyclicBarrier.count not a volatile? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf commented on EJBTHREE-2155: ----------------------------------------- It's because this piece of code throws a NPE sometimes: java.lang.NullPointerException at org.jboss.aop.InstanceAdvisorDelegate.getJoinpointAspect(InstanceAdvisorDelegate.java:263) at org.jboss.aop.InstanceAdvisorDelegate.getPerInstanceJoinpointAspect(InstanceAdvisorDelegate.java:215) at org.jboss.ejb3.interceptors.container.ManagedObjectAdvisor.getPerInstanceJoinpointAspect(ManagedObjectAdvisor.java:288) at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:158) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_328011903.invoke(InvocationContextInterceptor_z_fillMethod_328011903.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_328011903.invoke(InvocationContextInterceptor_z_setup_328011903.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) ... 29 more Thus the bean is never invoked and thus the worker tries to pickup the next task. Meanwhile the test case goes completely haywire. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf updated EJBTHREE-2155: ------------------------------------ Attachment: EJBTHREE-2155__fix_ThreadPool_stats.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/EJBTHREE-2155?page=com.atlassian.jira.plugi... ] Carlo de Wolf resolved EJBTHREE-2155. ------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira