ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarity: Intermittent System errors are occurring the Application and Background Servers


Article ID: 52725


Updated On:


Clarity PPM SaaS Clarity PPM On Premise



This problem may manifest as intermittent system errors in various Clarity pages or interruptions of jobs running on the bg-server. Inspection of the app-niku or bg-niku logs will show the following on Oracle.

SQL error code: 0
Error message: [CA Clarity][Oracle JDBC Driver]Connection reset by peer:
socket write error

The error will be similar for MS SQL Server.


The application server may have 2 Network Interface Cards(NIC's), and Clarity may not have a bind address specified. This could result in network traffic that originates from one NIC, but is received by the other, resulting sockets not receiving the expected data.

This problem can be easily corrected by specifying one of the NIC's network addresses as the bind address in the CSA's (Clarity System Administrator) properties tab.

Keywords: CLARITYKB, NIC, NSA, CSA, socket write error, connection reset by peer, JDBC.


Component: PPMENV