Are you running an old version of jboss that has jboss-auto.jcml? This can make your old mbeans come back to life to haunt you. Try deleting it if present.
> Are you running an old version of jboss that has
> jboss-auto.jcml? This can make your old mbeans come
> back to life to haunt you. Try deleting it if
Nope, I'm using JBoss 2.4 which has a jboss.jcml.
I think I'm beating a dead horse... all 2.x jbosses have jboss.jcml, which is what _you_ get to try to change for initial configuration. jboss-auto.jcml used to be there to save your dynamically changed configurations automatically without telling you. I think early 2.4 versions still had it. The main effect was that if you removed an mbean from jboss.jcml, you would discover it come back from the grave as jboss happily recreated it from jboss-auto.jcml, automatically saved from your last shutdown.
If this is really not it, look closely at your log to try to figure out where the configuration for it is coming from.
> If this is really not it, look closely at your log to
> try to figure out where the configuration for it is
> coming from.
Well, I think I figured out the problem -- sort of. Turns out, I don't need to use the Tyrex TransactionManager so I just commented it out of the jcml file. Now, I'm trying to figure out how to correctly decleare the default TransactionManager as a JNDI name. The errors I'm getting are:
[WARN,JNDIFactory] [JNDIFactory.getTransactionManager] Failed to find TransactionManager named java:comp/TransactionManager in JNDI.
In my jboss.jcml file, I have:
Do I also need to declare something else to the the TransactionManager registered in JNDI?
Thanks for your help.