Bit old this post, but I thought I'd post the reply as I've spent all day
fighting this. The problem stems from you using an ear file. if you seperate
your hibernate files and put them in a .har file it works fine. Not sure what
the solution is to including har in an ear and I've run out of t
I've sussed it now. You need to call the MBeanServer I was treating it like an
EJB. Thanks for the pointer.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854978#3854978
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=
private SearcherService getSearcherService(String serverName) throws
NamingException {
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(Context.URL_PKG_PREFIXES,
"
I have two identical MBeans on two servers. Each server has access to a
different file system, so I need to be able to use each mbean on each machine.
It seems to always use the local MBean, despite explicitly looking it up on
the other machines JNDI space.
Is this the same as EJB's defaulti
We're using 3.2.3. Sometime when we shutdown one of our clustered servers and then
bring it back up. It suffers from what we refer to as paranoid server syndrome. It
suspects another version of itself of being in the cluster. The other members in the
cluster also begin this loop too, they ne
