AnsweredAssumed Answered

Process Engine Issues - log file analysis

Question asked by CMCN1982 on Jul 14, 2014
Latest reply on Jul 14, 2014 by Suman Pramanik

Hi,

 

over the weekend we experienced an issue whereby one of our process engines stopped refreshing and scheduled jobs were impacted. The bg service didn't stop, but as the heartbeat was not refreshing we still encountered problems.

 

The following errors can be seen in the bg-ca.log file:

 

FATAL 2014-07-12 23:30:24,622 [Niku Job Scheduler (tenant=clarity)] union.persistence (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none) Failed to determine analytic function support

java.sql.SQLNonTransientConnectionException: [CA Clarity][SQLServer JDBC Driver]Connection reset by peer: socket write error

 

 

FATAL 2014-07-12 23:30:44,026 [Niku Job Scheduler (tenant=clarity)] union.persistence (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none)

com.ca.clarity.jdbc.sqlserverbase.dddx: SOCKETTIMEOUT

 

 

FATAL 2014-07-12 23:30:44,027 [Niku Job Scheduler (tenant=clarity)] union.persistence (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none) Failed to retrieve database version

java.sql.SQLNonTransientConnectionException: [CA Clarity][SQLServer JDBC Driver]Connection reset by peer: socket write error

 

 

FATAL 2014-07-12 23:30:44,027 [Niku Job Scheduler (tenant=clarity)] union.persistence (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none) Failed to determine analytic function support

java.lang.RuntimeException: Unexpected invocation exception: [CA Clarity][SQLServer JDBC Driver]Object has been closed.

 

 

FATAL 2014-07-12 23:30:44,028 [Niku Job Scheduler (tenant=clarity)] union.persistence (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none) Failed to determine driver vendor

java.lang.RuntimeException: Unexpected invocation exception: [CA Clarity][SQLServer JDBC Driver]Object has been closed.

 

 

FATAL 2014-07-12 23:30:44,028 [Niku Job Scheduler (tenant=clarity)] union.persistence (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none) Unsupported database version for vendor mssql

 

After these, we start to see:

 

 

ERROR 2014-07-12 23:30:47,029 [Niku Job Scheduler (tenant=clarity)] niku.njs (clarity:admin:197307377__ADDC5F85-CEE1-4C24-AB1F-B4AB1932D6D8:none) Error updating job in scheduler bg@NJROS1BBLA1067

com.niku.union.persistence.PersistenceException: Invalid or unavailable database

 

 

this error message repeated until we restarted the bg service.

 

The same issue occurred in our Development environment. It may be coincidence. but both servers affected are connected to the same switch. I'm trying to learn from our Server Ops team if any work was being carried out on this switch which could have lead to cause the errors generated above. Might this explain the problem?

Outcomes