Hide Forgot
project_key: JBEPP When I have JCR transaction, which seems to do many save/update operations, then JCR is not updated correctly and objects are not saved into JCR at all. This can happen during import of large organization-configuration.xml or portal-configuration.xml . Simple steps to reproduce: - Add 100 users into portal-configuration.xml into section "NewPortalConfigListener" and param "user.configuration" . I am attaching my portal-configuration.xml (Note: By default it's only root user here. Adding 100 new users will force listener to init default site for every user even if users does not exist in IDM database) - Run portal. After 5 minutes there is exception in server log (See attachement new-portal-config-exception.txt) because transaction is too long. (Seems that it only happens during large transactions where commit took 5 minutes or more) From thread dump, I am seeing that almost whole time from that 5 minutes is spent in JBoss cache during commit of JCR transaction.
Attachment: Added: portal-configuration.xml Attachment: Added: new-portal-config-exception.txt Attachment: Added: dump4.txt
Link: Added: This issue is related to JBQA-5399
I've tried some workarounds but nothing helped. What I've tried so far is: a) Disable managed transactions (Switch datasources to gatein-ds.xml to "no-local-tx" and in jcr-configuration.xml switch "always-managed" parameter to false) b) Disable SessionRegistry cleaner thread to change it to some big value in repository-configuration.xml (added attribute session-max-age): <repository name="repository" system-workspace="system" default-workspace="portal-system"> <security-domain>gatein-domain</security-domain> <access-control>optional</access-control> <session-max-age>3600000</session-max-age> <authentication-policy>org.exoplatform.services.jcr.impl.core.access.JAASAuthenticator</authentication-policy> c) Increase transactionTimeout from 300 to 3000 in server/default/deploy/transaction-jboss-beans.xml (No effect as JCR transaction is still cancelled after 5 minutes)
IMPORTANT POINT: I tried to downgrade JCR libs in EPP 5.2 ER1 in gatein.ear/lib from version from 1.14.0-GA to 1.14.0-CR4-CP01 and it helps to avoid initialization exception. So seems that problem is in JCR.
Release Notes Text: Added: Problem doesn't happen anymore with upgrade eXo JCR to 1.14.1-GA and related exo kernel, exo core and exo ws dependencies. This is done in EPP 5.2 by Jira JBEPP-1231 . So I am closing this for now.
Moving comment put in RN Text field to comment field: Problem doesn't happen anymore with upgrade eXo JCR to 1.14.1-GA and related exo kernel, exo core and exo ws dependencies. This is done in EPP 5.2 by Jira JBEPP-1231 . So I am closing this for now.
Release Notes Docs Status: Added: Not Required Release Notes Text: Removed: Problem doesn't happen anymore with upgrade eXo JCR to 1.14.1-GA and related exo kernel, exo core and exo ws dependencies. This is done in EPP 5.2 by Jira JBEPP-1231 . So I am closing this for now.