How do I run Integrity Check on Server Sockets and Acceptor Threads?
You can choose a value of socket time-outs and thread counts by analyzing statistics about sockets and threads, generated by Statistics and Diagnostics. This enables you to carry out a persistent integrity check on the number of threads and their health.
If there is a conflict between configured number of threads and number of existing threads, necessary steps are taken. If actual number of threads is more than the configured number, some threads are killed; if the actual number of threads is found to be less than the configured number then some new threads are created; if some threads are not alive, new threads are created. The functional details are described in the subsequent sections.
Persistent check on the health of Server socket is also carried out. The Server socket response time is measured. This helps in accessing the performance degradation of Server under load.
Integrity Check does not effect the performance of Server. Modules and properties such as server-config.xml, deploy-config.xml, MBeans, SPIs, ANT Handler, command line interface, Web Console etc. do not suffer any negative impact of integrity check.
What are the considerations for running Integrity Check for Acceptor Threads?
While running an integrity check on acceptor threads, the following factors are considered:
- Acceptor thread Count: It is the conflict between configured thread count and actual thread count. If actual thread count is more than the configured count, some of the acceptor threads will be terminated and if the actual thread count is found to be less than the configured count then some more acceptor threads will be created.
- State of threads: A persistent check is carried out on the health of threads. The dead threads are removed from the list and new threads are created to replace them.
What are the considerations for running Integrity Check for Sessions?
Integrity check considerations for a session are:
- Session count: This is the number of active session with the Server. Integrity check of actual sessions count and the PramatiTimerThread counts.
- Session closing: This includes the number of sessions that are closed after time-outs, the number of sessions closed by the client, and the number of sessions closed after invalidation.
What are the considerations for running Integrity Check for Sockets?
Integrity check considerations for Server sockets are:
- ServerSocket health: This is a persistent check on the health of a socket whether or not it is accepting requests.
- Response time: This is the current response time of the Server for a known request versus the time taken on load for the same request to detect degradation of performance.
- Socket closing: The number of sockets that are closed after time-out and by the client because of denial of service is checked.
Related Topics:
| 
