Tuning Connection Pool for production system

The most import tuning point of Tomcat is connection pool, because most service failures come between WAS and DBMS. Furthermore, tuning connection pool has the biggest impact on increasing WAS throughput. Tomcat has changed it's connection pool implementation from Apache DBCP to internal connection pool. (From Tomcat 7 both options are available) You can check … Continue reading Tuning Connection Pool for production system

About Tomcat’s default session manager

Tomcat's default session manager is "StandardManager". (org.apache.catalina.session.StandardManager) Without specific setting, StandardManager manages session data. Class hierarchy All session manager must implement Manager interface. (Cluster manager also implements Manager)   How StandardManager works? Usually, you create session as follows. What happens inside this code? HttpServletRequest.getSession() -> ApplicationHttpRequest.getSession() -> ManagerBase.createSession() -> StandardSession.setId() -> StandManager.add() Except HttpServletRequest, all … Continue reading About Tomcat’s default session manager

The problem of Tomcat session cluster

Some people said that Tomcat session cluster is not fit for high traffic web services. So I did performance test. (both DeltaManager and BackupManager) An ideal cluster is whose total TPS shows linear graph. But Tomcat session cluster showed log graph. (it's coefficient is dependent on usage pattern) I analyzed why it happened. The following … Continue reading The problem of Tomcat session cluster

About Tomcat session cluster

Servlet session on Tomcat is managed by "Tomcat manager". There are 3 kinds of session manager. Default manager (StandardManager) Delta manager Backup manager Default manager (StandardManager) is non clustered session manager. That is, sessions are not shared between Tomcat instances. Without specific setting, default manager is used when we use servlet session api. Delta manager … Continue reading About Tomcat session cluster