I have not included the setting for transaction support in my TreeCacheAop 
configuration because I have been getting errors when using the 
TransactionManagerLookupClass attribute, with either 
DummyTransactionManagerLookup or TransactionManagerLookup as this attribute's 
value.  I now expect that this absence of transaction support is why I do not 
get replication with the TreeCacheAop.


When I use the TransactionManagerLookup class for this attribute's value

 

  |         <attribute 
name="TransactionManagerLookupClass">org.jboss.cache.TransactionManagerLookup</attribute>
  | 
 

I get the following Exception:

 

  | 09:28:28,845 ERROR [TreeCacheAop] Starting failed 
jboss.cache:service=TreeCacheAop
  | 
  | java.lang.InstantiationException: org.jboss.cache.TransactionManagerLookup
  | 
  |         at java.lang.Class.newInstance0(Class.java:335)
  |         at java.lang.Class.newInstance(Class.java:303)
  |         at org.jboss.cache.TreeCache.startService(TreeCache.java:1089)
  |         at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
  |         at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
  |         at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
  |         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
  |         at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
  |         at 
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
  |         at 
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
  |         at $Proxy0.start(Unknown Source)
  | 
  |     etc...
  | 
 


When I use the DummyTransactionManagerLookup class (the original setting in the 
example syncRepl.xml) for this attribute's value

 

  |         <attribute 
name="TransactionManagerLookupClass">org.jboss.cache.TransactionManagerLookup</attribute>
  | 
 

I get the following Exception:

 

  | 09:37:22,322 ERROR [DummyTransactionManager] binding of 
DummyTransactionManager failed
  | 
  | javax.naming.NameAlreadyBoundException
  | 
  |         at org.jnp.server.NamingServer.bind(NamingServer.java:126)
  |         at org.jnp.interfaces.NamingContext.bind(NamingContext.java:501)
  |         at org.jnp.interfaces.NamingContext.bind(NamingContext.java:469)
  |         at javax.naming.InitialContext.bind(InitialContext.java:359)
  |         at 
org.jboss.cache.transaction.DummyTransactionManager.getInstance(DummyTransactionManager.java:41)
  |         at 
org.jboss.cache.DummyTransactionManagerLookup.getTransactionManager(DummyTransactionManagerLookup.java:17)
  |         at org.jboss.cache.TreeCache.startService(TreeCache.java:1094)
  |         at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
  |         at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
  |         at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
  |         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  |         at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
  |         at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
  |         at 
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
  |         at 
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
  |         at $Proxy0.start(Unknown Source)
  |         at 
org.jboss.system.ServiceController.start(ServiceController.java:416)
  | 
  |     etc...
  | 
 

One item of interest is that the TreeCacheAop still deploys OK when this error 
happens, in contrast to the failure to deploy which happens as a result of 
using the TransactionManagerLookup class for this attribute's value.

Any ideas on what causes these errors and/or how to get around them ?  Thanks 
in advance for any suggestions.


--James


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869219#3869219

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869219


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to