CPU usage of DOORS Next Generation server goes up to 100%
I just installed a DOORS Next Generation server.
Microsoft SQL Server 11.00.5058
IBM WebSphere Application Server 8.5.5.5
DOORS Next Generation 6.0
I found that sometimes the CPU usage of the server goes up to 100% without many users log on to the system.
In rm.log, I found the following.
Is it related to 100% CPU usage?
What might be the cause?
Microsoft SQL Server 11.00.5058
IBM WebSphere Application Server 8.5.5.5
DOORS Next Generation 6.0
I found that sometimes the CPU usage of the server goes up to 100% without many users log on to the system.
In rm.log, I found the following.
2015-11-05 17:06:35,415 [ ccm.jfs.indexer.triple.live] ERROR com.ibm.team.repository - CRJAZ2654E The server was unable to connect to the database because the database connection settings are invalid or because database is unreachable (SQLSTATE: 08S01, SQLCODE: 0). Verify the connection settings in your teamserver.properties file. See the Jazz Team Server log for more information.
com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset by peer: socket write error ClientConnectionId:e814f278-591b-48cd-a812-2b6f4f598f1f".
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1668)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1323)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset by peer: socket write error ClientConnectionId:e814f278-591b-48cd-a812-2b6f4f598f1f".
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1668)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1323)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)
Is it related to 100% CPU usage?
What might be the cause?
Accepted answer
It looks like the problem may have been caused by the indexer not being able to complete because of problems connecting to the database.
If you check all application logs, you might find that they all have the same error indicating there is a problem with the database connection.
Has your DBA has switched the SQL Server connection to use SSL?
The database is refusing connections and we are not able to finish indexing and causes the CPU to hit 100%.
If it is ok with your company's policy, you can switch SQL server to accept non-secure connection and see if the problem is resolved.