Skip to Content.
Sympa Menu

grouper-users - [grouper-users] RE: Connection pooling to reduce first load time after Tomcat start

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] RE: Connection pooling to reduce first load time after Tomcat start


Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: "Wessel, Keith" <>, "" <>
  • Subject: [grouper-users] RE: Connection pooling to reduce first load time after Tomcat start
  • Date: Tue, 4 Oct 2016 15:07:47 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:AGbQnRdSqONSyW4xr10o1T+ilGMj4u6mDksu8pMizoh2WeGdxc68Yh7h7PlgxGXEQZ/co6odzbGJ4+a9AidZvN6oizMrTt9lb1c9k8IYnggtUoauKHbQC7rUVRE8B9lIT1R//nu2YgB/Ecf6YEDO8DXptWZBUj22Dwd+J/z0F4jOlIz3krnqo9yAKzlP0XCCbKhpIRHy5Sbct9UWy8M2Kbk80QDEplNJf+BXw2RpPhSekwuqoo/684Rk7jxdobc87MNaSo37ebg1V7pVEG5gPmworoW/ugPEUBOC/D4BSWgMiTJJBRTI9hf3Qs23vyfn4LlTwi6faIfWXKI5Q3DqxKdxSQSiwHMCPD4o4mzNos1rh+RGuB+noVpyz5OCM9LdD+Z3Yq6IJYBSfmFGRMsEEnUZWo4=
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

I would bump that timeout up J (whether or not startup takes a while… you don’t want a request failing because of timeout… make it 60 seconds at least).  Also in your tomcat start script maybe you could prime the pump by hitting the servlet?  I think if I made a patch that implemented the init() method on the servlet and started grouper it would get grouper ready to go automatically, do you want that?  Btw, I don’t think changing pooling would help, need hibernate to init and classes to load, that’s the bottleneck I think

 

Thanks

Chris

 

From: [mailto:] On Behalf Of Wessel, Keith
Sent: Monday, October 03, 2016 4:35 PM
To:
Subject: [grouper-users] Connection pooling to reduce first load time after Tomcat start

 

Hi, all,

 

We’re running a fairly vanilla Grouper installation at this point, with few changes from what the Grouper Installer did. One change is that we’re talking to a remote MySQL database server instead of HSQL.

 

I’ve noticed, the first time we connect to Grouper after a Tomcat restart or after a while of inactivity, things take a while to return – usually longer than the 15 second time-out we have configured in Apache mod_proxy. That means that the first page load usualy results in a 503 from Apache.

 

How would I go about configuring connection pooling and starting up some initial connections on Tomcat start as well as a validation check and occasional retirement/regeneration of db connections? Is there a way to interface something like Tomcat CP or HikariCP with Grouper, or should I just use the options available in the MySQL Connector JAR?

 

Thanks,

Keith

 




Archive powered by MHonArc 2.6.19.

Top of Page