3.2 Technical Considerations in Operations Center v5.7

Operations Center Server and Dashboard Installations on Windows 2012 R2 Require JRE 1.8.0_51 or Earlier

If you are installing the Operations Center Server or dashboard on Microsoft Windows 2012 R2, you must use JRE 1.8.0_51 or earlier to run the installation program. After installation, you must use JRE 1.8.0_65 for the server and the dashboard.

MaxPermSpace in Java 1.8

With Java 1.8, the MaxPermSpace runtime option is no longer supported and is replaced with the -XX:MaxMetaSpaceSize option. When you install Operations Center, the setup program automatically sets the appropriate option based on the Java version that you are using.

Duplicate Index Entries in Liferay after Upgrade

If you upgrade from Operations Center v5.6 to v5.7, the first time you start the Operations Center server, the Liferay database attempts to create indexes that already exist and generates warnings similar to the following:

WARN com.liferay.portal.dao.db.BaseDB - The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.MBDiscussion' and the index name 'IX_F7AAC799'. The duplicate key value is (<NULL>, <NULL>).: create unique index IX_F7AAC799 on MBDiscussion (uuid_, groupId);

It is safe to ignore these warnings.

Lock Table Does Not Exist Warning after Upgrade

If you upgrade from Operations Center v5.6 to v5.7, the first time you start the Operations Center server, the Liferay database attempts to clear locks and generates warnings similar to the following:

WARN com.liferay.portal.events.StartupAction - Unable to clear locks because Lock table does not exist

It is safe to ignore these warnings.

Liferay 6 Does Not Support 2-1 (30/70) Page Layout

Liferay 6 does not support the 2-1 (30/70) page layout. If you configured a page with the 2-1 (30/70) page layout, to avoid losing the portlet, change the page to use any other layout before you upgrade to Operations Center v5.7.

New Default File Encoding for Tomcat Java Virtual Machine on Windows

The default file encoding for Tomcat Java Virtual Machine on Microsoft Windows platforms is now UTF-8. If you are upgrading from Operations Center v5.6 to v5.7, you must use the Dashboard Configuration Manager to add the command line option -Dfile.encoding=UTF8 to the Java Runtime Options field.

Unique Constraint Error after Upgrade for Dashboard with Oracle Database

If you upgrade from Operations Center v5.6 to v5.7 and you are using an Oracle database with the Dashboard, the first time you start the Operations Center server, Operations Center generates an error similar to the following:

2016-08-04 15:19:12,283 ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00001: unique constraint (SYSTEM.IX_C7057FF7) violated

It is safe to ignore this error.

Custom Themes Not Upgraded from Liferay 5.2.3 to Liferay 6.2

If you upgrade from Operations Center v5.6 to v5.7 and you are using custom themes, the custom theme content is not upgraded from Liferay Portal Standard Edition 5.2.3 to Liferay Portal Community Edition 6.2 CE GA4. After you upgrade to v5.7, you must manually upload and install the custom themes.

For information about uploading and installing custom themes, see Installing Additional Themes in the Operations Center Dashboard Guide.