1 Reply Latest reply on May 12, 2003 8:47 AM by Adrian Brock

    Message recovery may not be accurate

    basley Newbie

      using jboss 3.2.1 on Linux, many times when I restart jboss I have the following message :

      14:51:08,674 WARN [ServiceController] Problem starting service jboss.mq:service=PersistenceManager
      org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection is broken: Connection refused); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection is broken: Connection refused)))
      at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:276)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1299)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)

      Caused by: java.sql.SQLException: Connection is broken: Connection refused
      at org.hsqldb.Trace.getError(Unknown Source)
      at org.hsqldb.Trace.error(Unknown Source)
      at org.hsqldb.jdbcConnection.reconnectHSQL(Unknown Source)
      at org.hsqldb.jdbcConnection.openHSQL(Unknown Source)
      at org.hsqldb.jdbcConnection.(Unknown Source)
      at org.hsqldb.jdbcDriver.connect(Unknown Source)
      at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:147)


      Does someone know why and how to force hsql to restart ?

      thanks