We are working on an issue where the application eventually runs out of session resources on the database connection pool. We've set minimum connections = maximum connections as a short-term fix so that the pool size doesn't change, because we believe the leak occurs when the pool is resized. We are also working on the long-term fix, which is to put in a JNDI configuration to replace Jive's connection provider. Meanwhile, Jive is investigating a higher-level locking function on the connection. And we are running load tests on an iGate JDBC driver, which we hope to deploy this week for better compatibility with our SQL Server database. We are making these changes because the thread dumps indicate problems with database connectivity.
At the same time, we installed a new community test environment with Tomcat on a 32 win2003 platform. We are configuring that and will begin testing later in the week. If the driver replacement doesn't solve our problem, we will move replace Linux/Tomcat with the Win2003/Tomcat in order to run on a completely different JDBC environment which is more compatible with our Win2003 SQLServer database cluster.
We are also going to reset the system tonight at 5:00am to attempt to make it through the European peak demand.
Rich Text Editor (RTE): We plan to move the JavaScript for the RTE onto our Akamai service. Currently, most of the functionality is in a gzipped JavaScript library that is served from the Jive platform and unzipped by the browser. It appears that IE calls these JavaScript functions before they are fully unzipped, which results in the object not found errors many of you have reported. This problem is worse when the application is running slowly. By moving the files to Akamai, we will be able to serve them unzipped, and we believe this will greatly improve the editor loading issues.
Thank you for your patience as we work through these issues.
