We recently upgraded to 7.1.9 from 7.1.5 and are seeing very long Tomcat start times (almost an hour per node - we have 8 nodes). Additionally, we are seeing long report response times; so long that we've had to adjust the timeout for some reports to 240 seconds to get a response. We finished the upgrade last week, so more data has been added to our production database in that time but not such a significant amount that would cause such a huge degradation like this. Our database server hasn't changed and is still using the same Oracle version that we were using for 7.1.5, our Java version remains the same (our versions of Oracle and Java are supported according to the 719 Platform Support Guide). The only thing that changed (that we are aware of) is that passivation was removed from the file system and added to the database in 7.1.9.
Has anyone else seen a degradation of performance in 7.1.9? If so, what did you do to overcome it?
SR-A15047 was opened for this, and this entry was discovered in the alert log:
2015-12-12 07:28:54,558 GMT*8*PEGA0005*1579591*250*46b08fc3d37298123b45690c3870c1fc*NA*NA*AD9E047A8AFEB9B81010BB795994CF4BC*none*blank*null*b0f61728d0c0235b9979c284b05ec554*N*0*AD9E047A8AFEB9B81010BB795994CF4BC*46*ip-10-88-33-174*STANDARD*com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl*NA*(Engine Startup Init Services)********NA*NA*NA*NA*NA*initial Executable;0 additional frames in stack;*NA*Database operation took more than the threshold of 250 ms: 1,579,591 ms
SQL: select pzPVStream , pxCommitDateTime from RULES.pr_assign where pxObjClass = ? order by pzInsKey