[Building Sakai] tomcat 7 threads maxing out , freezing Sakai instance

[Matthew Buckett]

On 25 March 2014 08:04, David Wafula Wanyonyi <
DavidWafula.Wanyonyi at wits.ac.za> wrote:

>  It seems to me the issue stems from these hardcoded values in
> /sakai-2.9.2-all/kernel/kernel-component/src/main/webapp/WEB-INF/db-components.xml
>

Any property of a spring bean can be set through sakai.properties, if you
look in db-components.xml you'll see the bean ID for these properties and
then you can set the values by using the format property at beanId=value.


> I can't find where they are set dynamically.
>     ......
>
>         <!--  The initial number of connections that are created when the
> pool is started. -->
>         <property name="initialSize">
>             <value>10</value>
>         </property>
>

Setting this can be done through a line in sakai.properties of:

initialSize at javax.sql.dbcp.BaseDataSource=50

When you next have sakai lockup it may be worth looking at what the
connections are doing, a simple way of doing this with MySQL is using the
MySQL Workbench which allows you to view client connections and their
current queries:

http://www.mysql.com/products/workbench/

or from the command line with SHOW PROCESSLIST

http://dev.mysql.com/doc/refman/5.1/en/show-processlist.html

-- 
  Matthew Buckett, VLE Developer, IT Services, University of Oxford
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140325/fd3c70b2/attachment.html