MDB doesn't rebind after JBOSS MQ recover ------------------------------------------ Key: EJBTHREE-779 URL: http://jira.jboss.com/jira/browse/EJBTHREE-779 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: EJB 3.0 RC9 - FD Environment: Solarisx86, JDK1.5_06 , jboss4.0.5.GA Reporter: Ramil Israfilov Priority: Critical Fix For: EJB 3.0 RC10 - FD I have an MDB which is described using annotations: @Depends("jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider") @MessageDriven(name = "EJBExecutorMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/certione/ExecutorQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4"), @ActivationConfigProperty(propertyName = "dLQMaxResent", propertyValue = "4"), @ActivationConfigProperty(propertyName = "SubscriptionDurability", propertyValue = "Durable") }, messageListenerInterface=MessageListener.class) public class EJBExecutorMDB implements MessageListener { ... } I deploy it in clustered environment with HAJNDI and clustered JBOSS MQ. So far so good. Then cluster node on which JBOSS MQ is running crashed MDB is not rebind. From log file I see that JBOSS MQ successfully restarted on second node. And all permamnet queue destinations (defined in config files) are available, but destinations which are defined in annotations don't exist. And in log file I see that server constantly tries bind MDB, but got alway the same error: javax.naming.NameNotFoundException: queue/certione/ExecutorQueue at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155) at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy249.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.util.naming.Util.lookup(Util.java:215) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:399) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:306) at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:250) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.onException(AbstractDLQHandler.java:94) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1348) at java.lang.Thread.run(Thread.java:595)

MDB doesn't rebind after JBOSS MQ recover ------------------------------------------ Key: EJBTHREE-779 URL: http://jira.jboss.com/jira/browse/EJBTHREE-779 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: EJB 3.0 RC9 - FD Environment: Solarisx86, JDK1.5_06 , jboss4.0.5.GA Reporter: Ramil Israfilov Priority: Critical Fix For: AS 4.2.0 GA I have an MDB which is described using annotations: @Depends("jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider") @MessageDriven(name = "EJBExecutorMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/certione/ExecutorQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4"), @ActivationConfigProperty(propertyName = "dLQMaxResent", propertyValue = "4"), @ActivationConfigProperty(propertyName = "SubscriptionDurability", propertyValue = "Durable") }, messageListenerInterface=MessageListener.class) public class EJBExecutorMDB implements MessageListener { ... } I deploy it in clustered environment with HAJNDI and clustered JBOSS MQ. So far so good. Then cluster node on which JBOSS MQ is running crashed MDB is not rebind. From log file I see that JBOSS MQ successfully restarted on second node. And all permamnet queue destinations (defined in config files) are available, but destinations which are defined in annotations don't exist. And in log file I see that server constantly tries bind MDB, but got alway the same error: javax.naming.NameNotFoundException: queue/certione/ExecutorQueue at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155) at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy249.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.util.naming.Util.lookup(Util.java:215) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:399) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:306) at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:250) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.onException(AbstractDLQHandler.java:94) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1348) at java.lang.Thread.run(Thread.java:595)

MDB doesn't rebind after JBOSS MQ recover ------------------------------------------ Key: EJBTHREE-779 URL: http://jira.jboss.com/jira/browse/EJBTHREE-779 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: EJB 3.0 RC9 - FD Environment: Solarisx86, JDK1.5_06 , jboss4.0.5.GA Reporter: Ramil Israfilov Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 4.2.1 I have an MDB which is described using annotations: @Depends("jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider") @MessageDriven(name = "EJBExecutorMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/certione/ExecutorQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4"), @ActivationConfigProperty(propertyName = "dLQMaxResent", propertyValue = "4"), @ActivationConfigProperty(propertyName = "SubscriptionDurability", propertyValue = "Durable") }, messageListenerInterface=MessageListener.class) public class EJBExecutorMDB implements MessageListener { ... } I deploy it in clustered environment with HAJNDI and clustered JBOSS MQ. So far so good. Then cluster node on which JBOSS MQ is running crashed MDB is not rebind. From log file I see that JBOSS MQ successfully restarted on second node. And all permamnet queue destinations (defined in config files) are available, but destinations which are defined in annotations don't exist. And in log file I see that server constantly tries bind MDB, but got alway the same error: javax.naming.NameNotFoundException: queue/certione/ExecutorQueue at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155) at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:258) at $Proxy249.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.util.naming.Util.lookup(Util.java:215) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:399) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:306) at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:250) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.onException(AbstractDLQHandler.java:94) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1348) at java.lang.Thread.run(Thread.java:595)