Yes, mbeans dropped into farm are just independently distributed instances. They
wouold have to be XMBeans with a clustered persistence manager with custom
interceptors to snych changes.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Hello,
I´m trying to deploy an MBean in a cluster using JBoss
3.2.1.
I´ve already tested the cluster configuration and
everything works fine. But when I put a sar file
inside the 'farm' directory, it is only deployed in
the local JBoss.
Is it possible to have a clustered MBean? If it is,
what
Not sure of the issue, but go get 3.2.2RC2. 3.2.2RC1
and now RC2 have fixed clustering issues. Try it in
this container first, see if it works. If it does,
then you probably came across a bug with 3.2.1. If
not, then on with the answers..
--- Mauricio De Diana [EMAIL PROTECTED]
wrote:
Hello,
Thanks, Kevin. Thanks, Scott.
I think I´ll have to figure out a simpler way to have
the MBean state synchronized. Maybe I can store the
MBean state in an EJB (statefull session bean or an
entity bean).
Thanks,
Mauricio De Diana
--- Scott M Stark [EMAIL PROTECTED] escreveu:
Yes, mbeans
Thanks, Kevin. Just upgrading my JBoss has solved the
farm problem.
But now I have another one:
I copy a sar file (with a jboss-service.xml inside) to
the farm directory and it is correctly deployed in the
nodes of my cluster.
Then I use the jmx-console in node 1 to set an MBean
attribute.
When I
Are they stateful of stateless? I honestly have never
messed with the console and changing attributes.
Didn't even know you could do that. That is kewl. I
would say that the clustering still has work to do.
When 3.2.2 is final, hopefully all these issues will
be fixed. You may want to try the
