I have gained access to the Tomcat manager and see that the jasperserver app is listed but is not started. when I try to start the all I get the following (and a whole bunch more) in the log files: catalina.out log: and catalina.2012-07-22.log Code:catalina.out log:2012-07-22 17:02:55,553 WARN JDBCExceptionReporter,http-8080-1:100 - SQL Error: 0, SQLState: null2012-07-22 17:02:55,558 ERROR JDBCExceptionReporter,http-8080-1:101 - Cannot create PoolableConnectionFactory (Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.)2012-07-22 17:02:55,560 WARN SettingsFactory,http-8080-1:133 - Could not obtain connection to query metadataorg.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)and catalina.2012-07-22.logJul 22, 2012 5:02:59 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartJul 22, 2012 5:02:59 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver] startup failed due to previous errorsJul 22, 2012 5:02:59 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [Thread-13] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:02:59 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-0] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:02:59 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:02:59 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [quartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:03:30 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartJul 22, 2012 5:03:30 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver] startup failed due to previous errorsJul 22, 2012 5:03:30 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [Thread-16] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:03:30 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-0] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:03:30 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.Jul 22, 2012 5:03:30 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/jasperserver] appears to have started a thread named [quartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak.