We're running JBossCache in a standalone app (no JEE container) in a clustered
configuration. Is the DummyTransactionManagerLookup not the correct TMLookup to
use? Are there standalone JTS implementations? What's the best way to properly
use REPL_SYNC without running inside a JEE app server?
Vi
Umm, yeah. Ignore my last post, I'm an idiot. :)
I forgot implements ReadOnlyCacheJmxWrapperMBean in my subclass, so naturally
JMX exposed the CacheJmxWrapperMBean instead. Duh!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065422#4065422
Reply to the post
So, I tried writing a ReadOnlyCacheJmxWrapperMBean with just getters, along
with a ReadOnlyCacheJmxWrapper class which subclassed CacheJmxWrapper. I was
very surprised to see JMX use the CacheJmxWrapperMBean interface rather than my
ReadOnlyCacheJmxWrapperMBean.
So I basically had to write out
Sorry I didn't check JIRA first, I was in a hurry.
Thanks for the subclass tip. I'm new to MBeans and didn't quite realize that
would be so easy to do, but now that you mention it that would be pretty easy
and should work just fine. I'll try that in the morning.
Thanks.
View the original post
I'm experimenting with CacheJmxWrapper and found a difference compared to the
CacheFactory. We normally use this code:
CacheFactory factory =
DefaultCacheFactory.getInstance();
| Cache cache = factory.createCache( configFile,
false );
If I try to use the getCache() method of CacheJmxWrapper,
"[EMAIL PROTECTED]" wrote : Is your concern that the CacheJmxWrapperMBean
interface has too much? If you post an MBean interface you want, I can look
into creating a limited super-interface that you could expose. No promises
though.
Our concern is that people could change the cache configuratio
Oops, I forgot: This is 2.0.0 CR3 on Sun JDK 1.6.0_02 in a stand-alone app
compiled to 1.5 target VM. We're trying to use Spring for configuration, rather
than programmatic configuration.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063198#4063198
Reply to
We want to expose some of the interceptors via JMX, but don't want to expose
the functionality of CacheJmxWrapper's setters and methods. I've tried quite a
few ways of doing this, but I can't figure it out. Is this not possible?
View the original post :
http://www.jboss.com/index.html?module=bb
Well, thanks for fixing it. I've been told we can't change the JBoss code, for
license reasons (whatever that means), so I'll just have to figure out some
kind of hack until another release comes out.
Thanks for the quick response.
View the original post :
http://www.jboss.com/index.html?modul
