5 Replies Latest reply on Oct 27, 2006 5:39 PM by Jake

    Persistence Manager Fails to Start - Clues to look for

    Jake Newbie

      I have a jboss based application from a vendor. I've modified the configuration (with the vendor's assistance) to permit multiple instances of jboss to run, under different users. Recently I reinstalled one of the instances, and it subsequently failed to start.

      I have since been through all of the diagnostics I can think of to discover what the problem is, and now I'm out of ideas. I'm ready for a fresh supply of ideas if anyone has any suggestions.


      Sun V880 running Solaris 9, 16Gb RAM, 100Gb+ disk space. Plenty of available disk.

      JBoss [WonderLand] 3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)

      Three instances completely separate, no shared ports, databases etc. Configurations appear to have been generated by the method cited in the documentation, setting ports_default, ports_01, ports_02 etc up as environments and specifying which configuration set to choose by naming it in jboss-service.xml.

      Two instance continue to run normally. Luckily one is my production instance and the others are used for preparation and testing. One instance consistently refuses to start up. Set logging level to debug in log4j. As the startup sequence unrolls, the system beigns to start server/default/deploy/jms/hsqldb-jdbc2-service.xml. In deploying the components this depends on, it appears to fail as it starts the persistence Manager. The error message centers around this:

      23:42:30,785 ERROR [PersistenceManager] Starting failed
      org.jboss.mq.SpyJMSException: Could not get a connection for jdbc2 table construction ; - 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:268)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1356)

      System resources appear to be untaxed. I have used SQLPlus from the application account to access the Oracel database this application accesses.

      What can I do now to get more information?