2 Replies Latest reply on Mar 11, 2005 8:57 AM by xavierpayne2

    entry for transaction <HOSTNAME:4510>:2 not found in transac

    xavierpayne2 Newbie

      What might be the reason for receiving the following exception?

      java.lang.Exception: entry for transaction <HOSTNAME:4510>:2 not found in transaction table
       at org.jboss.cache.interceptors.CacheStoreInterceptor$SynchronizationHandler.afterCompletion(CacheStoreInterceptor.java:255)
       at org.jboss.tm.TransactionImpl.doAfterCompletion(TransactionImpl.java:1418)
       at org.jboss.tm.TransactionImpl.completeTransaction(TransactionImpl.java:1090)
       at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:349)
       at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:454)
       at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:322)
       at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:146)
       at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:123)
       at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
       at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
       at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
       at org.jboss.ejb.Container.invoke(Container.java:870)
       at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:413)
       at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:82)
       at $Proxy74.authenticate(Unknown Source)


      I am using normal TreeCache (not the aop one) as an MBean inside of JBoss 4.0.1 using REPL_SYNC with isolation level set to REPEATABLE_READ (I have also tried SERIALIZABLE)

      I have tried the 1.2 stable jar and the latest from cvs and received the same error. We use JBoss Cache extensively throughout our architecture so tracing it to the exact cause is proving very difficult for us. Any ideas?

      We have two TreeCache MBeans loaded (on persisted via the jdbc cache loader. The other has no cache loader) and in some places we are using them both. Could that cause problems?