⁠Chapter 4. Known Issues

Portal

1065452 - Domain mode cluster: Cannot sign into portal

private

It was found that the configuration in domain.xml file was incorrect. This caused issues with signing into portal while running 2-node cluster in domain mode. The workaround is to remove the following snippet from domain.xml in high availability and full-high availability profiles:

​<login-module code="org.exoplatform.web.login.FilterDisabledLoginModule" flag="required"> <module-option name="portalContainerName" value="portal"/> <module-option name="realmName" value="gatein-domain"/> </login-module>
​code

1117945 - Default value of property "jboss.as.management.blocking.timeout" (300 s) may be insufficient for portal startup with more data

private

A new class was introduced in the Application Server version JBoss Portal consumes. The class loads a parameter value set by jboss.as.management.blocking.timeout, or defaults to 300 (seconds) if not overridden in standalone.xml or standalone-ha.xml. This default value was identified as causing an issue during portal start-up if the portal takes more than 300 sec. This default value was identified as causing an issue during portal start-up if the portal takes more than 300 seconds (5 minutes) to start up. Possible reasons for this may include slow database performance or large amounts of data. Increasing the value to 7200 (two hours) corrected the issue. Initially starting with 3600 (one hour) was not sufficient time for loading performance testing data, however this value may prove suitable in some production environments.

1064245 - a4j:push is not working with WSRP

a4j:push is not compatible with WSRP. The URL rewrites performed by the JavaScript code of the Richfaces component is not compatible with the way WSRP evaluates the resource location.

1192273 - SAML2: Portal as SP and IDP - Failed to locate configuration file /WEB-INF/conf/sso/saml/picketlink-idp.xml

Due to an update to PicketLink, the location of the SP and IDP XML files have to be specified using an absolute path or a relative path to JBOSS_HOME/bin. To specify an absolute path, add a system property such as {jboss.home.dir} and the affected property entry is gatein.sso.saml.config.file

1194018 SSO:OpenAM 12 - Logout redirection doesn't work

The new OpenAM UI, called XUI cannot complete the logout procedure. To resolve the issue, use the legacy UI by disabling XUI. To disable XUI in OpenAM, access the, "OpenAM administration console", access "Configuration", select "Core" and uncheck the option "XUI interface". See, Administration and Configuration guide, chapter 14.4. Configuring the Platform as an OpenAM Client.

1078270 Dialect detection doesn't work for Oracle 12

Hibernate does not auto-detect Oracle 12 database and this could cause exception during JBoss Portal boot. To use Oracle 12 database for JCR, set the property gatein.jcr.datasource.dialect to value org.hibernate.dialect.Oracle10gDialect in the file $JBOSS_PORTAL_HOME/standalone/configuration/gatein/configuration.properties.

To use Oracle 12 database for IDM (Identity Management), set the property hibernate.dialect to value org.hibernate.dialect.Oracle10gDialect in the file $JBOSS_PORTAL_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/idm-configuration.xml.

Oracle 10 Dialect can be used without issues with an Oracle 12 database.

1191580 INFO IJ000311: Throwable from unregister connection: java.lang.IllegalStateException: Trying to return an unknown connection2!

It was found that the test logs contained several occurrences of IJ000311 messages during the testing of scenarios related to the management of users and roles. This is caused if lazyStartOfHibernateTransaction configuration parameter is set to true due to which the connection is obtained lazily in a context of a portlet application but returned in the context of the main portal servlet which has a different context. Given that the underlying Connection Manager lends/registers and accepts the connections back based on the contexts this leads to the named message. The message itself is harmless as the lending and returning of the connections works properly and there are no connections leak under any circumstances.