Are you starting the JBOSS server with a "clustered" configuration? ie the "all" configuration ?
What version of JBOSS are you using ?
Have you tried @Clustered(loadBalancePolicy="RoundRobin") ? (Note the quotes and String type instead of class)
Jboss version is 4.2.3.
Jboss cluster: Actually Jboss is more customized in our product and i think yes. but not sure if i am missing any configuration. we actually have custom configuration for the product (instead of "all").
yes, I tried. (giving string value is throwing compilation error).
@Clustered(loadBalancePolicy = RoundRobin.class)
any suggestions to explore more on this?
Thanks for responding to my query.
when a @Clustered EJB deployed in a non clustered profile, this error occurs. you can try it in the all profile, if it works, you need to customize the all profile from scratch.
I had that error before and that was the cause.
jboss q wrote:
when a @Clustered EJB deployed in a non clustered profile, this error occurs.
Is that the case with AS-5.x and later too? I would have expected it to ignore that annotation if the profile doesn't support clustering.
Yes, after adding the jboss cluster service xml into deploy folder and adding jbossha.jar to lib folder, this error has disappeared.
And now the client complains with the "Caught: java.lang.RuntimeException: cluster invocation failed" error.D:\projects\groovy>groovy hello.groovyCaught: java.lang.RuntimeException: cluster invocation failed, last exception was:at hello.run(hello.groovy:68)
My bad, server bind address was 0.0.0.0. that caused that error.
Its working finally. I see load being balanced to multiple servers in round robin fashion.