Sorry for not replying for a while, but I was analyzing the logfiles and trying
to reproduce the behaviour we have on our production system. Thanks to the
answers here I think I understand now better what is going on, and I indeed
found a way to reproduce the behaviour.
First, I was wrong in
Thanks very much for your reply. I examined the logfiles again to answer your
questions:
[EMAIL PROTECTED] wrote : 1) You refer to the master node. Please confirm
that this is 62.50.43.211.
|
No, at that time the master node was 62.50.43.210. The first logoutput and the
second one are
OK, things are a bit clearer. Don't know the full answer yet but we're getting
there.
jkressin wrote :
| But the most intersting question for me is: Even if the (Master-)node lost
some viewchanges, why does it suddenly undeploy the (HA-)queues and
(HA-)topics?
They are undeployed
1) You refer to the master node. Please confirm that this is 62.50.43.211.
2) On the node that produced the first bit of logging in your post, do you see
log entries with this content New cluster view for partition StagePartition:
202 and New cluster view for partition StagePartition: 201?
3)
Make sure your client is accessing a connection factory using the HAJNDI and not the
local JNDI. If your client is using the wrong port number for the local instead of
the HA then you can get this exception when the name you are looking for is really i9n
the HA and not the local.
View the
http://www.jboss.org/wiki/Wiki.jsp?page=JBossMQHA
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3851559#3851559
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3851559
---
