We are about to use this library in production and I had some queries for that from monitoring standpoint:
what is the way to monitor any issues with it like
connection failing to hz cluster
any particular log which we can use to track failure to find a particular jsession id
any log we can monitor for any failure related to read/write to the cluster. I am presuming this will be on a separate thread than the thread processing the request due to deferredWrite being 'true' (the default behavior as I see in README.md)
what is the behavior when any of the failure happens? Does it start using the local tomcat storage as done with org.apache.catalina.session.StandardManager implementation? Or does it fail the functionality altogether?
sertugkaya
commented
3 years ago
We are about to use this library in production and I had some queries for that from monitoring standpoint:
what is the way to monitor any issues with it like
what is the behavior when any of the failure happens? Does it start using the local tomcat storage as done with org.apache.catalina.session.StandardManager implementation? Or does it fail the functionality altogether?