1 Reply Latest reply on May 20, 2003 12:48 AM by Bernd Zeitler

    could not passivate ?

    Sven Do Newbie

      I'm using hsqldb 1.7.1 and it works fine so far. However, if jboss tries to passivate my ejb - I get:

      "javax.ejb.EJBException: Could not passivate; causedByException is: org.jboss.resource.adapter.jdbc.local.LocalConnection ...."

      Because of "....jdbc.local.LocalConnection" I assume the problem is caused by the jdbc-datasource. Any ideas or suggestions?

        • 1. Re: could not passivate ?
          Bernd Zeitler Expert

          Your bean must be properly serializable. If you are holding a connection, it isn't.
          The resolution depends on what you are trying to do. Probably you don't have to hold the connection at all. Just look up a new one every time you need it. JBoss is doing the pooling. At least you should release the connection on ejbPassivate(). You can look up the new one on ejbActivate().