2 Replies Latest reply on Mar 18, 2003 8:42 AM by Marcus Brito

    IllegalStateException: Trying to return an unknown connectio

    Marcus Brito Novice

      Hello, folks!

      I'm getting a very strange error since I updated to JBoss 3.2.0RC2 this morning. This keep getting to the console:
      [pre]java.lang.IllegalStateException: Trying to return an unknown connection2! org.jboss.resource.adapter.jdbc.WrappedConnection@14d0183
      at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:274)
      at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:550)
      at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:280)
      at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:97)
      at com.telebahiacelular.movistore.dao.DAOMoviOraAb.closeConnection(DAOMoviOraAb.java:137)
      at com.telebahiacelular.movistore.dao.DAOMoviOraAb.closeConnection(DAOMoviOraAb.java:128)
      at com.telebahiacelular.movistore.seguranca.inspetor.dao.InspetorOra.getFiltroLoja(InspetorOra.java:259)
      at com.telebahiacelular.movistore.dao.DAOMoviOraAb.getFiltroLoja(DAOMoviOraAb.java:197)
      at com.telebahiacelular.movistore.atendimento.prioridade.dao.PrioridadeTipoAtendDAOOra.selecionarPorFiltro(PrioridadeTipoAtendDAOOra.java:311)
      ...[/pre]
      and this:
      [pre]14:38:42,071 INFO [CachedConnectionManager] Could not find a close method on alleged connection objects. Please close your own connections.
      java.lang.Exception: Stack Trace
      at org.jboss.resource.connectionmanager.CachedConnectionManager.closeAll(CachedConnectionManager.java:357)
      at org.jboss.resource.connectionmanager.CachedConnectionManager.popMetaAwareObject(CachedConnectionManager.java:199)
      at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:190)
      at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77)
      at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:108)
      at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:243)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:104)
      at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:208)
      at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:154)
      at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:322)
      at org.jboss.ejb.Container.invoke(Container.java:652)
      at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)
      at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:88)
      at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:77)
      at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80)
      at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:109)
      at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:82)
      at $Proxy92.selecionarPorFiltro(Unknown Source)
      ...[/pre]
      However, I'm *sure* i'm closing my connections and this didn't happen in RC1. There really is something wrong with my application or this is a bug introduced in RC2? And if the second option is true, is a workaround?

      This maybe something related, but there is now a warning in the console while starting RC2 that wasn't there in RC1:

      [pre]14:37:26,423 INFO [LocalTxConnectionManager] Starting
      14:37:26,424 WARN [LocalTxConnectionManager] ----------------------------------------------------------
      14:37:26,425 WARN [LocalTxConnectionManager] ----------------------------------------------------------
      14:37:26,425 WARN [LocalTxConnectionManager] Please change your datasource setup to use TransactionManagerService with object name jboss.tm:service=TransactionManagerService
      14:37:26,426 WARN [LocalTxConnectionManager] instead of TransactionManager with value java:/TransactionManager
      14:37:26,426 WARN [LocalTxConnectionManager] ----------------------------------------------------------
      14:37:26,427 WARN [LocalTxConnectionManager] ----------------------------------------------------------[/pre]

      Any help? Any hints?