Created attachment 924214 [details] stacktrace Description of problem: I cannot start portal configured to use JTA (two separate XA Datasources) according to https://docs.jboss.org/author/display/GTNPORTAL38/JTA+integration with IBM DB2 Stacktrace attached. There is link to log: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/EPP/view/6.2/view/UI%20Database%20Support/job/epp6_ui_selenium_tests_db_db2-97/135/console
It's failing due to the usage of same database. See https://bugzilla.redhat.com/show_bug.cgi?id=1126863#c2
After further investigation it seems this problem comes from JCR when it's datasource is configured as XA with DB2. There is no apparent problem with IDM ds. In MW lab you can find the portal installation used to reproduce the issue (owned by user hudson). /qa/services/hudson/static_build_env/jpp6/issues/db2_jta_jcr/jboss-portal-6.2
To reproduce the issue it should be sufficient to configure the JCR datasource as XA. https://docs.jboss.org/author/display/GTNPORTAL38/JTA+integration This is an example JCR ds config for our DB2 (v9.7.0.8) instance: <xa-datasource jndi-name="java:/gatein-jcr_portal" pool-name="GateInDS-JCR" enabled="true" use-java-context="true"> <xa-datasource-property name="ServerName">vmg06.mw.lab.eng.bos.redhat.com</xa-datasource-property> <xa-datasource-property name="DatabaseName">jbossqa</xa-datasource-property> <xa-datasource-property name="PortNumber">50000</xa-datasource-property> <xa-datasource-property name="DriverType">4</xa-datasource-property> <xa-datasource-class>com.ibm.db2.jcc.DB2XADataSource</xa-datasource-class> <driver>db2jcc4.jar</driver> <security> <user-name>eppuidb2</user-name> <password>eppuidb2</password> </security> <xa-pool> <min-pool-size>10</min-pool-size> <max-pool-size>50</max-pool-size> <prefill>true</prefill> </xa-pool> <statement> <prepared-statement-cache-size>32</prepared-statement-cache-size> <share-prepared-statements>true</share-prepared-statements> </statement> </xa-datasource>
Created attachment 926452 [details] JDBC driver: IBM DB2 Enterprise e9.7 (FP8) Used jdbc driver: IBM DB2 JDBC Universal Driver Architecture 4.14.122 (FP8)
Created attachment 926522 [details] stacktrace - 6.1.0 This setup doesn't work in 6.1 and 6.1.1 either but there is a different exception.
Thanks for checking, Tomáš! That makes it a non-blocker for JBoss Portal 6.2. Moving target release to 6.3.0.
Linked an upstream Jira https://jira.exoplatform.org/browse/JCR-2335
Note: This issue is still present in Portal 6.2.0.ER8 which has downgraded JCR to version 1.15 compared to 6.2.0.ER4 which has JCR 1.16.