[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Changes on the JBM stack on JBoss5

[vblagojevic@jboss.com]

Hi,

You guys correctly point to the source of the problem which is a group that could not be flushed during getState call. I first thought that is a transient problem, however I was confused when I saw that you are not using FLUSH in your stack, are you?

Anyway, the root cause is that the cluster could not be flushed for whatever underlying reason that might have happened and therefore the state retrieval did not proceed. You have the following options:

a) keep things as they are - catch the exception on getState. The state will not be transferred to a joining node
b) use another getState method where a parameter useFlushIfPresent is set to false. Cluster will not be flushed for state transfer in that case.

I am not familiar with message ordering and state semantics that have to be satisfied in JMS. Are you familiar with FLUSH? There is a good summary here [1]. You might not need to flush the cluster during state transfer. Let us know.

Regards,
Vladimir

[1] http://www.theserverside.com/tt/articles/article.tss?l=NewFeaturesJGroups



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187705#4187705

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187705