OK, my ignorance is revealed. XML override of the clustering configuration
will not work in 4.0.4.GA; you'd need to upgrade the EJB3 implementation to
EJB3 RC9, where support for xml override was added -- see
http://jira.jboss.com/jira/browse/EJBTHREE-569[/url] . Sorry for not knowing
this ea
OK, so what's happening is you're not getting a cluster-aware client proxy
(i.e. the proxy isn't failing to do what its designed for, it's not the correct
type of proxy.) So I'll figure out why that is; I ran some tests yesterday w/o
problem, but my config was slightly different from yours.
Vi
So the stack trace is the same as in
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91094...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975941#3975941
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975941
I run two servers, then start the client, but all requests are executed on one
server (whereas with annotated beans requests go sequentially to both servers).
When I stop server executing requests, I get the following exception on the
client:
Exception in thread "main" java.lang.reflect.Undeclar
Please post the stack trace of the exception you're seeing.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975876#3975876
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975876
___
Brian,
I've tried to skip -D variables, but result was the same. It looks like cluster
configuration in jboss.xml is completely ignored.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975674#3975674
Reply to the post :
http://www.jboss.com/index.html?module
There's another recent post describing a failover problem with EJBs configured
with XML -- see
[url]http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973991#3973991
[/url].
We're investigating the cause.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=
Your config looks OK. Do things work correctly if you skip the
-Djboss.partition.name=... i.e. just accept DefaultPartition?
There is a JIRA to make the value of the @Clustered partitionName attribute
configurable via a system property -- se
http://jira.jboss.com/jira/browse/EJBTHREE-424 . At
