CMS Snapshot Analysis - Compute Snapshot - Fatal Error - Connection has been closed

Description

This page will provide you explanation and solution about this Fatal Error message that appears in the CAST MS log file :

ERR: 2017-01-24 10:49:14: This connection has been closed.
                            com.castsoftware.java.ExternalException:This connection has been closed.
                              com.castsoftware.connection.JdbcConnection.throwException(JdbcConnection.java:1156)
                              com.castsoftware.connection.JdbcConnection.prepareCall(JdbcConnection.java:947)
...
                              java.lang.Thread.run(Thread.java:744)
                            Connection Error: { call <Local_DB>.DSS_UNLOCK (?) }
                              com.castsoftware.java.InternalException:Connection Error: { call <Local_DB>.DSS_UNLOCK (?) }
                                org.postgresql.jdbc2.AbstractJdbc2Connection.checkClosed(AbstractJdbc2Connection.java:822)
                                org.postgresql.jdbc3.AbstractJdbc3Connection.prepareCall(AbstractJdbc3Connection.java:316)
                                org.postgresql.jdbc2.AbstractJdbc2Connection.prepareCall(AbstractJdbc2Connection.java:308)
 ...
                                com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:82)
                                com.castsoftware.java.treatment.Task.run(Task.java:275)
                                com.castsoftware.java.treatment.TaskExecutor$TaskMainThread.run(TaskExecutor.java:135)
                                java.lang.Thread.run(Thread.java:744)

Observed in CAST AIP

ReleaseYes/No
8.3.x✅
8.2.x✅
8.1.x✅
8.0.x✅

Observed on RDBMS

RDBMSYes/No
Oracle Server✅
Microsoft SQL Server✅
CSS3✅
CSS2✅

Step by Step Scenario

  1. Package the source code and run the snapshot.
  2. The compute snapshot is failing

Action Plan

The connection to the Database server has been closed. It happens because of network issues, or if the Database server has shut down abruptly.

  1. Check that the Database Server is connected by checking that the corresponding service in still up or by connecting an IDE (like PGAdmin) to the database server.
  2. If the Database server is down, you must restart it.
  3. Run the snapshot again to check if the issue persists.

Impact on Analysis Results and Dashboard

Snapshot fails

Notes/comments