Issue: Must delete temporary files (V4.2SP3 and SQL Server)
Summary
When using a Microsoft SQL Server relational database, temporary files are created and stored in the Windows TEMP directory every time Process Commander is initialized. Eventually, these may cause initialization to fail.
Update : This issue does not occur with V4.2SP4 and later releases. The workaround presented here applies to V4.2SP3 and earlier releases.
The workaround is to clear out these files from the TEMP directory regularly, to be sure there is enough space for Process Commander's start-up temporary files.
Suggested Approach
When Process Commander uses a Microsoft SQL Server relational database, it creates temporary files in the TEMP directory every time Process Commander is initialized. For example, starting the Process Commander server creates ten of these files.
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error setting up static cursor cache.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseImplSortCursorResultSet.setupTempFile(Unknown Source)
at com.microsoft.jdbc.base.BaseImplSortCursorResultSet.postSetupInitialize(Unknown Source)
at com.microsoft.jdbc.base.BaseResultSet.<init>(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.commonGetNextResultSet(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery(Unknown Source)
at com.microsoft.jdbc.base.BaseDatabaseMetaData.getPrimaryKeys(Unknown Source)
at com.pega.pegarules.engine.database.DatabaseTableMap.lookupTableInfo(DatabaseTableMap.java:258)
at com.pega.pegarules.engine.database.DatabaseTableMap.get(DatabaseTableMap.java:180)
at com.pega.pegarules.engine.database.ClassMap.init(ClassMap.java:741)
at com.pega.pegarules.engine.database.DatabaseImpl.<init>(DatabaseImpl.java:456)
at com.pega.pegarules.engine.context.PRThreadImpl.<init>(PRThreadImpl.java:204)
at com.pega.pegarules.engine.context.PRRequestorImpl.getThread(PRRequestorImpl.java:656)
at com.pega.pegarules.engine.context.PRRequestorImpl.setRulesetsAndRoles(PRRequestorImpl.java:860)
at com.pega.pegarules.engine.context.PRRequestorImpl.initializeRequestor(PRRequestorImpl.java:840)
at com.pega.pegarules.engine.context.PRRequestorImpl.<init>(PRRequestorImpl.java:218)
at com.pega.pegarules.engine.context.PRNodeImpl.createRequestor(PRNodeImpl.java:347)
at com.pega.pegarules.engine.context.PREnvironment.initialize(PREnvironment.java:211)
at com.pega.pegarules.engine.context.PREnvironment.getInstance(PREnvironment.java:157)
at com.pega.pegarules.engine.context.PREnvironment.getInstance(PREnvironment.java:139)
at com.pega.pegarules.web.PRStartup.init(PRStartup.java:174)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:916)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3266)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3395)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:614)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:343)
at org.apache.catalina.core.StandardService.start(StandardService.java:388)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:506)
at org.apache.catalina.startup.Catalina.start(Catalina.java:781)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
Previous topic Issue: Cannot use SQL keywords as database column names Next topic Issue: Must restart application server after database server restart