Knowledge Base >> Defects that May Require Upgrade to Ignite PI 7.0.32

Defects that May Require Upgrade to Ignite PI 7.0.32 - Confio Article 1577

Confio Article: 1577 Published: Nov 17 2009 11:42 AM
Version: < 7.0.32 Topic(s): Install and Setup Ignite Management
Database(s): All

Defects that May Require Upgrade to Ignite PI 7.0.32

In versions of Ignite PI earlier than 7.0.32, inefficient use of memory and other resources has resulted in errors in some high utilization or small server environments.  Ignite PI 7.0.32 introduces numerous fixes that address these issues, and Confio recommends that customers upgrade to 7.0.32 to avoid interruptions in Ignite availability.   Note that there is no impact on monitored systems, only on operation of the Ignite PI application.  

 

Who is Affected

All Ignite PI versions from PI 4.3 up through PI 7.0.29 may affected.   Older Ignite 6.X systems are not affected (but Ignite 6.X sites should plan to upgrade to PI anyway!).

 

Resolution

In particular, if any of the following problems are experienced, the upgrade to 7.0.32, either Windows or UNIX/Linux should be completed ASAP.   Supported customers can download these versions by logging into http://support.confio.com .  (Make sure you get these production versions from the Support site, not the trial software from the www marketing site.)   For specific questions or problems, contact support@confio.com .

 

Symptoms:  Error Messages

These are not full error messages but important snippets that can be used to search the error log:

1.   Monitor for database [<database_name>] failed in job [PublishJob] due to [PI detected future monitoring data…

2.   Unable to get the SQL text:

com.confio.iwc.repository.exceptions.RepositoryDatabaseAccessTimeoutException: A time out occurred while executing a query against the database instance holding the Ignite Repository

3.    The existence of any errors in the log that include the following text:  java.lang.OutOfMemoryError

4.   java.lang.IllegalStateException: Underlying datasource has not been set.

 

How to Know if you Have a Problem

To search the logs for these errors, click on the main Log link at the top-right corner of the GUI.  On the Log page click the Advanced button to allow searches against the Ignite logs and ensure “All” is selected in the Database/App list box:

Click the Apply Filter button after entering these search terms in the Contains Exact Phrase field:
1.    PI detected future monitoring data
2.    com.confio.iwc.repository.exceptions.RepositoryDatabaseAccessTimeoutException
3.    java.lang.OutOfMemoryError
4.    Underlying datasource has not been set