Cannot access Jaspersoft console. JSP Tomcat log has a very long exception.

Document ID : KB000009169
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

I am unable to access the Jaspersoft Console. When I check the Jaspersoft Tomcat log, I see a very long exception listed, indication some connection issues. What could be the problem? 

Environment:
LINUX RHEL 7.2JASPERSOFT UNIFIED DASHBOARDS 6.3
Cause:

In the long exception a message can be found indicating a potential connection issue with postgresql database (default database installed.) 

 Caused by: org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. 

 

A portion of the full exception: 

 

2018-01-22 14:20:17,943 ERROR ContextLoader,localhost-startStop-1:331 - Context initialization failed 
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'themeSource' defined in ServletContext resource [/WEB-INF/applicationContext-themes.xml]: Cannot resolve reference to bean 'themeCache' while setting bean property 'themeCache'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'themeCache' defined in ServletContext resource [/WEB-INF/applicationContext-themes.xml]: Cannot resolve reference to bean 'unsecureRepositoryService' while setting bean property 'repositoryService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepositoryService' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'proHibernateRepositoryListeners' while setting bean property 'repositoryListeners'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'proHibernateRepositoryListeners' defined in ServletContext resource [/WEB-INF/applicationContext-report-options.xml]: Cannot resolve reference to bean 'schedulingReportDeleteListener' while setting constructor argument with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulingReportDeleteListener' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportSchedulingService' while setting bean property 'schedulingService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingService' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Cannot open connection 

Resolution:

There are several reasons this error may occur: 

-> PostgreSQL isn't running 

-> PostgreSQL isn't listening for TCP/IP connections (listen_addresses in postgresql.conf) 

-> PostgreSQL is listening on a different port to the one you're connecting on 

 

1. First step is to verify PostgreSQL is running. A TOP should list the process. If not, you can also run a NETSTAT on default PostgreSQL port 5432 to see if the port is connecting. 

If PostgreSQL is not running, you can start it using the available startservers.sh script: 

<CABI INSTALL DIR>/startServers.sh

2. You can also verify default port 5432 is open by running NETSTAT -ano | grep -i 5432

3. Check local IP tables are turned off/disabled

4. Check external firewall rules for potential blocking port 5432

5. The address and port configuration are located in <CABI INSTALL DIR>/postgresql/data/postgresql.conf. Verify the port setting is correct.

6. Run a sniffer trace to check connection to PostgreSQL database

Additional Information: