[JBoss JIRA] Created: (GTNPORTAL-855) javax.transaction.RollbackException when creating navigation node in GateIn
by Marek Posolda (JIRA)
javax.transaction.RollbackException when creating navigation node in GateIn
---------------------------------------------------------------------------
Key: GTNPORTAL-855
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-855
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: GateIn trunk (revision 2083) deployed on EAP5,
Sun JDK 1.6,
MySQL 5.1 shared database (between two GateIn nodes)
Reporter: Marek Posolda
Fix For: 3.1.0
I have a problem when having two GateIn instances on different servers running in cluster. Steps to simulate:
1) Run node1 with -Dexo.profiles=cluster
2) Run node2 with -Dexo.profiles=cluster
3) Login as root in node1 and go to portalnavigation -> Edit navigations -> Add node -> Use existing page in page selector (portal::classic::homepage) -> Fill node name and title -> click to Save
4) Now I am able to see my new node. But I can see exceptions in server logs in both node1 and node2.
Exception on node2 is "[TxInterceptor] prepare failed! java.lang.NullPointerException".
Exception on node1 is "[TxIsolatedOperation] Transaction has been rolled back javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could not commit transaction."
Full stacktraces of both exceptions are attached. Interesting is that I am also able to see the page on second node. So it seems that nothing happens in application itself, only exceptions in server logs are strange. Exception on node2 (NullPointerException) occurs first and exception "RollbackExcption" on node1, where new navigations were created, occurs after it. And I can see only when having cluster with more nodes. It doesn't occur in single node.
For completeness: I am using shared database MySQL with JBoss datasources in server/production/deploy directory and "no-tx-datasource" datasource. Both nodes are executed with "-Dexo.profiles=cluster". I am attaching my server/production/conf/gatein/configuration.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1134) Initialize component org.exoplatform.groovyscript.text.TemplateService during AS startup
by Marek Posolda (JIRA)
Initialize component org.exoplatform.groovyscript.text.TemplateService during AS startup
----------------------------------------------------------------------------------------
Key: GTNPORTAL-1134
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1134
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Performance
Affects Versions: 3.0.0-GA
Environment: GateIn trunk (revision 2755) deployed on EAP 5.0.1,
Sun JDK 1.6
Reporter: Marek Posolda
TemplateService is not initialized during JBoss server startup but it's initialized lazily when first accessed from org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(line 108). Problem can occur if more threads will try to send first HTTP request to GateIn in same time because Lifecycle.renderTemplate is called by more threads concurrently and now TemplateService is constructed independently by more threads in same time. To avoid this issue, TemplateService should implement Startable interface, so that it will be started directly during GateIn boot.
This can be usually seen in server log during startup of performance test:
[JBoss] 03:35:19,457 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:19,528 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:19,658 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:19,706 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:19,734 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:19,759 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:19,798 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:19,861 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:19,891 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:20,039 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:20,072 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:20,105 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:20,143 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:20,278 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:20,313 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:20,459 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:20,491 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:20,602 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:20,645 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:20,818 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:20,861 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:21,026 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:21,059 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:21,092 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:21,145 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:21,281 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:21,396 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:21,425 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:21,452 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
[JBoss] 03:35:21,537 INFO [ExoCacheFactoryImpl] The cache 'TemplateService' will be created with 'class org.exoplatform.commons.cache.SimpleExoCacheCreator'.
[JBoss] 03:35:21,594 INFO [ExoCacheFactoryImpl] The configuration template will be used for the the cache 'TemplateService'.
.............................
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month