Case #94733: Significant Performance / Frequent Unavailability of Jive SBS at our site


Description:


We are having significant performance problems and frequent unexpected outages of our Jive SBS installation which is severely impacting our business. This has happened both prior to and since we upgraded to the 4.0 release of SBS. The problem seems to have got worse in the past week or two since the students have been coming back to start the new academic year. We had to restart SBS roughly once a day last week, and we've had to do it twice today.

 

The symptoms are that SBS seems to get slower and slower, to the point where it seems to be unusable. Occasionally it seems to recover, but on most occasions it requires a restart to bring it back to a usable state. The load average on the SBS server doesn't seem to increase, although we have noticed that there is an SBS thread which is consistently consuming a whole CPU core.

 

ps -eFl shows a single thread which in a roughly 3 hour period, has accumulated 2h:58m of CPU time;

 

jive      7723     1  8992 97  141 12:28 pts/1    02:58:34 /usr/local/jive/java/bin/java -XX:+PrintClassHistogram -XX:+PrintTenuringDistribution -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xloggc:/usr/local/jive/var/logs/sbs-gc.log -Djava.security.egd=file:///dev/urandom -Xmx2048m -Xms2048m -XX:MaxPermSize=512m -Djive.home=/usr/local/jive -Djive.instance.home=/usr/local/jive/applications/sbs/home -Djive.name=sbs -Djive.context= -Djive.logs=/usr/local/jive/var/logs -Djive.application=/usr/local/jive/applications/sbs/application -Djive.work=/usr/local/jive/var/work/sbs -Djive.app.cache.ttl=10000 -Djive.app.cache.size=10240 -Dserver.port=9000 -Dhttp.addr=127.0.0.1 -Dhttp.port=9001 -Dhttp.monitor.addr=127.0.0.1 -Dhttp.monitor.port=9002 -Dlog4j.configuration=file:///usr/local/jive/applications/sbs/conf/log4j.properties -Dapp.cluster.jvmroute=node0 -Dtangosol.coherence.clusteraddress=224.224.224.224 -Dtangosol.coherence.clusterport=9003 -Dcatalina.base=/usr/local/jive/applications/sbs -Dcatalina.home=/usr/local/jive/tomcat -Djava.io.tmpdir=/usr/local/jive/var/work/sbs -classpath /usr/local/jive/applications/sbs/bin//bootstrap.jar:/usr/local/jive/applications/sbs/bin/tomcat-juli.jar::/usr/local/jive/java/lib/tool.
jar org.apache.catalina.startup.Bootstrap start

jive      7723     1  8992 97  141 12:28 pts/1    02:58:34 /usr/local/jive/java/bin/java -XX:+PrintClassHistogram -XX:+PrintTenuringDistribution -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xloggc:/usr/local/jive/var/logs/sbs-gc.log -Djava.security.egd=file:///dev/urandom -Xmx2048m -Xms2048m -XX:MaxPermSize=512m -Djive.home=/usr/local/jive -Djive.instance.home=/usr/local/jive/applications/sbs/home -Djive.name=sbs -Djive.context= -Djive.logs=/usr/local/jive/var/logs -Djive.application=/usr/local/jive/applications/sbs/application -Djive.work=/usr/local/jive/var/work/sbs -Djive.app.cache.ttl=10000 -Djive.app.cache.size=10240 -Dserver.port=9000 -Dhttp.addr=127.0.0.1 -Dhttp.port=9001 -Dhttp.monitor.addr=127.0.0.1 -Dhttp.monitor.port=9002 -Dlog4j.configuration=file:///usr/local/jive/applications/sbs/conf/log4j.properties -Dapp.cluster.jvmroute=node0 -Dtangosol.coherence.clusteraddress=224.224.224.224 -Dtangosol.coherence.clusterport=9003 -Dcatalina.base=/usr/local/jive/applications/sbs -Dcatalina.home=/usr/local/jive/tomcat -Djava.io.tmpdir=/usr/local/jive/var/work/sbs -classpath /usr/local/jive/applications/sbs/bin//bootstrap.jar:/usr/local/jive/applications/sbs/bin/tomcat-juli.jar::/usr/local/jive/java/lib/tool.

jar org.apache.catalina.startup.Bootstrap start

 

This thread always seems to be manipulating a PDF file. It appears to be the same file even when we restart SBS.

 

(produced using ls -l /proc/7723/fd/ | grep pdf )

lr-x------ 1 jive cspl 64 Sep 29 15:34 384 -> /usr/local/jive/var/work/sbs/tmp4856422043465074316.pdf

Latest Comment: Oct 19, 2010 3:28 AM by Andrew.Beresford

Comments

Case Product Issues

Loading Jira issues

Loading related product issues for this case

More Like This