Failover working for JMS Client but not for Statless Session

[bfach]

Hello,

I have a standalone java app connecting to JBoss 4.2.2.GA with jboss messaging 1.4.0SP3 installed.

JBossA and JBossB are started on seperate machines.

When the standalone java app is connected to JBossA, JBossA is killed and failover takes place and succeeds for the JMS messaging however the connection to a previously looked up stateless session bean does not failover over.

Is there a specific conifiguration property that needs to be set in order for failover to occur for session beans?

Thanks in advance,

[brian.stansberry]

You have to add

<clustered>true</clustered>

for each bean in jboss.xml. Or, if it's EJB3 you can add an @org.jboss.annotation.ejb3,Clustered annotation to the bean class.

[bfach]

bstansberry,

Thanks for the help. It appears that adding the jboss.xml to the META-INF directory of the jar within the ear with the clustered attribute fixes the problem. I attempted the same with the annotation however failover did not work for this bean.

Any idea what could cause this?

Thanks!

[brian.stansberry]

It was an EJB3 bean, right? Trying the annotation with an EJB2 bean is the only reason I know of why it wouldn't work when xml does.

[justkeys]

Perhaps you forgot your client should use the HA-jndi to lookup the bean = use port 1100, not 1099 in the Context.PROVIDER_URL property of the jndi context.