This content has been marked as final.
Show 7 replies
-
1. Re: JBoss Messaging Failover problems
clebert.suconic Jul 21, 2008 12:52 PM (in response to agohar)but when i kill or shutdown master node, the other node is not able to take over deploy the queues on it.
Are you deploying all your queues on both nodes?
That seems a dumb question, but I was confused since you mentioned the "master node" term.
This is a concept we might change in JBM 2, but unless this is a nomenclature you choose at your architecture, JBM 1.4 doesn't have the concept of master-backup node. Every node is active and once one node "dies" the other/next node will get the data merged. -
2. Re: JBoss Messaging Failover problems
agohar Jul 22, 2008 4:15 AM (in response to agohar)Are you deploying all your queues on both nodes?
Yes, i am deploying queues on both nodes. But when first is killed or properly shutdown, the other one doesn't deploy the queues whereas it is able to deploy the singleton scheduler deployed in deploy-hasingleton directory.
Any idea?
Thanks -
3. Re: JBoss Messaging Failover problems
agohar Jul 22, 2008 4:27 AM (in response to agohar)I am using JBoss-4.2.2, if it helps?
Thanks -
4. Re: JBoss Messaging Failover problems
mlange Jul 22, 2008 4:32 AM (in response to agohar)Are you using the clustered postoffice (true)?
-
5. Re: JBoss Messaging Failover problems
agohar Jul 22, 2008 9:37 AM (in response to agohar)I am using JbossMQ
Looking at the logs, it looks like the DLQ queues are failing only. and i repeatedly get the following error for queue/DLQ and all my application defined DLQ queues2008-07-22 10:54:32,989 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@15a0316(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@1fb580 destination=topic/refreshRulesTopic isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) 2008-07-22 10:54:32,990 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@15a0316(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@1fb580 destination=topic/refreshRulesTopic isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) javax.naming.NameNotFoundException: queue/DLQ at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242) at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155) at sun.reflect.GeneratedMethodAccessor138.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:312) at $Proxy314.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
any hint?
Thanks -
6. Re: JBoss Messaging Failover problems
ataylor Jul 22, 2008 9:50 AM (in response to agohar)This is the JBoss Messaging forum, you should post you're problem on the JBossMQ forum.
-
7. Re: JBoss Messaging Failover problems
agohar Jul 22, 2008 10:08 AM (in response to agohar)This is the JBoss Messaging forum, you should post you're problem on the JBossMQ forum.
oops wrong forum.
Cheers :-)