Stuart Douglas [https://community.jboss.org/people/swd847] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/725443#725443 -------------------------------------------------------------- In AS 7.1.1 you can use @DependsOn for singleton beans, to make sure that other EJB's don't shut down until the the singleton has shut down. Even though the spec says that you can only use this to reference other singleton beans, we have expanded this so you can reference any type of bean.  In AS7 upstream I have added a feature where you can use use @DependsOn on any session bean (not just singletons), AS7 upstream also has some other fixes to make sure that the EJB Client context does not shut down until all EJB's have shut down. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/725443#725443] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Maycon Oliveira [https://community.jboss.org/people/FuinhaAzul] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/725609#725609 -------------------------------------------------------------- The problem still happen.  Can you confirm ? Maybe I coded something wrong? *Just hit ctrl + c when the "STOP SERVER NOW!!!!" message shows* and the exception will happen. Here is my test: (I cleaned up the @DependsOn beacause I tried a lot of combinations and the problem persist, where I put this annotation?) @Singleton @Startup public class InitializerBean {               @EJB           private FirstSessionBean firstSessionBean;               @PostConstruct           public void init() {                     try {                               firstSessionBean.someOperation();                     } catch (Exception e) {                               e.printStackTrace();                     }           } } @Stateless @LocalBean public class FirstSessionBean {               @EJB           private SecondSessionBean secondSession;               public void someOperation() {                     try {                               // while (true) {                               System.out.println("STOP SERVER NOW!!!!");                               Thread.sleep(5000);                               secondSession.someOperation();                               System.out.println("INVOCATION COMPLETED");                               // }                     } catch (Exception e) {                               System.out.println("INVOCATION FAILED! ");                               e.printStackTrace();                     }           }               @PreDestroy           public void destroy() {                     System.out.println("FirstSessionBean.destroy");           }     } @Stateless @LocalBean public class SecondSessionBean {               public void someOperation() {                     System.out.println("Some operation");           }               @PreDestroy           public void destroy() {                     System.out.println("SecondSessionBean.destroy");           } } If you guys prefer, I have uploaded the eclipse project and the ejb.jar file: http://www.4shared.com/file/-1q3LQtw/file.html http://www.4shared.com/zip/cG3YjHs_/file.html -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/725609#725609] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

David Lloyd [https://community.jboss.org/people/dmlloyd] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/725619#725619 -------------------------------------------------------------- In your example, I believe you should add @DependsOn("SecondSessionBean") to the class declaration of FirstSessionBean. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/725619#725619] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

David Lloyd [https://community.jboss.org/people/dmlloyd] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/725642#725642 -------------------------------------------------------------- OK then there's probably still a bug in the implementation.  We'll look into it. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/725642#725642] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Stuart Douglas [https://community.jboss.org/people/swd847] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/725788#725788 -------------------------------------------------------------- I think I can see what is happening here, the EJB that is currently being invoked is shutting down, even though there is an active invocation, as StrictMaxPool does not wait for active invocations to finish. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/725788#725788] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jason Greene [https://community.jboss.org/people/jason.greene] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/730422#730422 -------------------------------------------------------------- There is a fix that was change into upstream that makes ejb shutdown more graceful. Combined with @DependsOn this should resolve the issue. Give the latest snapshot a try: http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-7.x-latest/la... http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-7.x-latest/la... -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/730422#730422] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Veit Guna [https://community.jboss.org/people/veitg] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/819639#819639 -------------------------------------------------------------- Hi. Can someone confirm/deny that this fix was included in the 7.1.3 final tag? I'll tried that with 7.1.3 final where I use @DependsOn in an MDB that references an EJB (non-singleton). Currently on shutdown, when a message is currently processing, it throws: {code} 13:53:16,943 ERROR [org.jboss.as.ejb3] javax.ejb.EJBTransactionRolledbackException: JBAS014559: Invocation cannot proceed as component is shutting down 13:53:16,943 ERROR [org.jboss.as.ejb3.invocation] JBAS014134: EJB Invocation failed on component EventProcessor for method public abstract void javax.jms.MessageListener.onMessage(javax.jms.Message): javax.ejb.EJBTransactionRolledbackException: JBAS014559: Invocation cannot proceed as component is shutting down     at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:137) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:202) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:188) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:42) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:43) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:184) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:181) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at javax.jms.MessageListener$$$view5.onMessage(Unknown Source) [jboss-jms-api_1.1_spec-1.0.1.Final.jar:1.0.1.Final]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_27]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_27]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_27]     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_27]     at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:142) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at $Proxy100.onMessage(Unknown Source)    at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:311)     at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1028)     at org.hornetq.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50)     at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1173)     at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27]     at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27] Caused by: javax.ejb.EJBException: JBAS014559: Invocation cannot proceed as component is shutting down     at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:37) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:181) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]     at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final] {code} Any chance that this dependency can also be defined via jboss-deployment-structure.xml somehow as an alternative? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/819639#819639] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]