Bug 1126859 - JTA separate DS - DB2
Summary: JTA separate DS - DB2
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR01
: 6.3.0
Assignee: mposolda
QA Contact: vramik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-05 13:16 UTC by vramik
Modified: 2015-03-10 13:32 UTC (History)
4 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
stacktrace (11.69 KB, text/x-log)
2014-08-05 13:16 UTC, vramik
no flags Details
JDBC driver: IBM DB2 Enterprise e9.7 (FP8) (3.63 MB, application/x-java-archive)
2014-08-13 14:09 UTC, Tomas Kyjovsky
no flags Details
stacktrace - 6.1.0 (14.30 KB, text/plain)
2014-08-13 16:50 UTC, Tomas Kyjovsky
no flags Details


Links
System ID Priority Status Summary Last Updated
EXO WCM JIRA JCR-2335 None None None Never

Description vramik 2014-08-05 13:16:18 UTC
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

Comment 2 mposolda 2014-08-06 15:39:24 UTC
It's failing due to the usage of same database. See https://bugzilla.redhat.com/show_bug.cgi?id=1126863#c2

Comment 3 Tomas Kyjovsky 2014-08-12 14:45:17 UTC
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

Comment 4 Tomas Kyjovsky 2014-08-13 14:07:15 UTC
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>

Comment 5 Tomas Kyjovsky 2014-08-13 14:09:49 UTC
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)

Comment 6 Tomas Kyjovsky 2014-08-13 16:50:19 UTC
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.

Comment 7 Peter Palaga 2014-08-14 08:32:55 UTC
Thanks for checking, Tomáš! That makes it a non-blocker for JBoss Portal 6.2. Moving target release to 6.3.0.

Comment 8 Peter Palaga 2014-08-20 13:43:08 UTC
Linked an upstream Jira https://jira.exoplatform.org/browse/JCR-2335

Comment 9 Tomas Kyjovsky 2015-03-10 13:32:44 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.