Liferay Portal 6.1 EE GA3 Known Issues

This article is a legacy article. It applies to previous versions of the Liferay product. While the article is no longer maintained, the information may still be applicable.

The following comprises a list of known issues associated with Liferay Portal 6.1 EE GA3.


Liferay Portal 6.1. EE GA3 contains the following known issues:

  1. PACL (Portal Access Control List) can cause issues on an upgrade
    • To work around this, turn off PACL when upgrading (set “” in
    • This issue will be corrected in an upcoming fix pack
  2. Staging not functional for DB2 database
    • This issue will be corrected in an upcoming fix pack
  3. Error thrown upon upgrade or fresh database start: Table 'DATABASE.portalpreferences' does not exist
    • This message is generated by the PDF converter initialization which doesn't have the configuration before the upgrade or creating the database.
    • The message is safe to ignore.
  4. JDK5 and Websphere 6.1 are not supported with Liferay 6.1 EE GA3
  5. Creation of sample data by the create-*.sql scripts causing errors
    • e.g. ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
    • This is caused by duplicate keys in the Layout (uuid_, groupId) index.
    • To avoid this issue, start up the portal with an empty database. This will automatically populate the default data correctly.
    • If this option is not available, use the "create-minimal.sql" script. This is functioning correctly (however it will not create the sample data).
  6. Marketplace Portlet download link is not working for large portlets (e.g. Kaleo)
    • This issue arises because of the way dl.file.max.size is checked in GA3 (3 MB is default)
    • For a workaround:
    1. Go to Server Admin
    2. Click File Upload Tab,
    3. Change the Maximum File Size for Documents and Media (for example, add zeros at the end)
    • After you save the changes, the portlet will deploy properly.
Was this article helpful?
0 out of 0 found this helpful