[Deploying Sakai] database load in 2.9

[Omer A Piperdi]

We have disabled portal chat. We are recently seeing connection timed 
out error like below..

java.sql.SQLRecoverableException: IO Error: Connection timed out
         at 
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1065)
         at 
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
         at 
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3584)
         at 
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3665)
         at 
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1352)
         at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
         at 
org.sakaiproject.db.impl.BasicSqlService.dbWriteCount(BasicSqlService.java:1247)
         at 
org.sakaiproject.db.impl.BasicSqlService.dbWrite(BasicSqlService.java:1143)
         at 
org.sakaiproject.db.impl.BasicSqlService.dbWrite(BasicSqlService.java:1059)
         at 
org.sakaiproject.event.impl.UsageSessionServiceAdaptor$ClusterStorage.closeSession(UsageSessionServiceAdaptor.java:981)

Also we have seen one of our app. server starts closing the sessions on 
other servers as orphan sessions and it stopped writing to sakai_event 
table.. We are not sure whether it is an issue with /dev/random on app. 
server. We plan to add '-Djava.security.egd=file:/dev/urandom' option at 
Tomcat startup.

Thanks
Omer


On 9/13/2012 6:35 PM, Sam Ottenhoff wrote:
> Are any other schools on 2.9.x like Rice willing to share info?  Have 
> you enabled new features that are disabled by default like portal 
> chat?  My assumption is that 2.9 like 2.8 (with optional features 
> disabled) would represent continued performance improvement.
>
> The only major performance improvement that has been merged since 
> Rutgers migrated to 2.9.x is KNL-934 (authz query improvements from VT 
> as discussed at the conference TCC meeting).
>
> --Sam
>
> On Wed, Sep 12, 2012 at 8:02 AM, Hedrick Charles <hedrick at rutgers.edu 
> <mailto:hedrick at rutgers.edu>> wrote:
>
>     We had a database performance problem the first week in Sept. Last
>     year our database server ran 10 - 20% load, now and then up to
>     30%. This year it was doubt that. 60% average indicates we don't
>     have enough to handle peaks, and in fact user performance was bad.
>
>     This wasn't such a big deal, because I had a new server ready. I
>     just accelerated moving it into production. It's possible that
>     something about our load has changed, but it could also indicate a
>     greater database load for 2.9.
>
>     _______________________________________________
>     production mailing list
>     production at collab.sakaiproject.org
>     <mailto:production at collab.sakaiproject.org>
>     http://collab.sakaiproject.org/mailman/listinfo/production
>
>     TO UNSUBSCRIBE: send email to
>     production-unsubscribe at collab.sakaiproject.org
>     <mailto:production-unsubscribe at collab.sakaiproject.org> with a
>     subject of "unsubscribe"
>
>
> !DSPAM:2294,50526db4128426909914249!
>
>
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
> !DSPAM:2294,50526db4128426909914249!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20120913/c09d2abc/attachment.html