Return-Path: 
 <commits-return-32353-apmail-tomee-commits-archive=tomee.apache.org@tomee.apache.org>
X-Original-To: apmail-tomee-commits-archive@www.apache.org
Delivered-To: apmail-tomee-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 33FAD1136F
	for <apmail-tomee-commits-archive@www.apache.org>;
 Tue, 16 Sep 2014 07:40:34 +0000 (UTC)
Received: (qmail 46213 invoked by uid 500); 16 Sep 2014 07:40:34 -0000
Delivered-To: apmail-tomee-commits-archive@tomee.apache.org
Received: (qmail 46184 invoked by uid 500); 16 Sep 2014 07:40:34 -0000
Mailing-List: contact commits-help@tomee.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@tomee.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@tomee.apache.org>
List-Post: <mailto:commits@tomee.apache.org>
List-Id: <commits.tomee.apache.org>
Reply-To: dev@tomee.apache.org
Delivered-To: mailing list commits@tomee.apache.org
Received: (qmail 46174 invoked by uid 500); 16 Sep 2014 07:40:34 -0000
Delivered-To: apmail-openejb-commits@openejb.apache.org
Received: (qmail 46171 invoked by uid 99); 16 Sep 2014 07:40:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 07:40:34 +0000
Date: Tue, 16 Sep 2014 07:40:34 +0000 (UTC)
From: "Oliver Guenther (JIRA)" <jira@apache.org>
To: commits@openejb.apache.org
Message-ID: <JIRA.12737435.1409228682000.42564.1410853234004@Atlassian.JIRA>
In-Reply-To: <JIRA.12737435.1409228682000@Atlassian.JIRA>
References: <JIRA.12737435.1409228682000@Atlassian.JIRA>
 <JIRA.12737435.1409228682020@arcas>
Subject: [jira] [Updated] (TOMEE-1337) Usage of
 com.mysql.jdbc.jdbc2.optional.MysqlXADataSource in Tomee 1.7.0 not possible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/TOMEE-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Guenther updated TOMEE-1337:
-----------------------------------
    Attachment: wrong-source-with-username.png

Nope, adding a extra user name and password, doesn't change anything.
The Datasource still points to the default hsqldb, not the configured mysql

> Usage of com.mysql.jdbc.jdbc2.optional.MysqlXADataSource in Tomee 1.7.0 not possible
> ------------------------------------------------------------------------------------
>
>                 Key: TOMEE-1337
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1337
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Debian GNU/Linux 7.x 64bit
> Oracle Java 8u20 64 bit 
> Mysql 5.5.38
>            Reporter: Oliver Guenther
>            Priority: Critical
>         Attachments: catalina.out, wrong-source-with-username.png, wrong-source.png
>
>
> If you want to use the mysql xa datasource, the configuration parameters are ignored.
> To reproduce:
> Install mysql 5.5
> Install tomee.
> Create a database in mysql.
> Modify the tomee.xml like this.
> {code:xml}
> <Resource id="repairDataSource" type="javax.sql.DataSource">
>   JdbcDriver com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
>   JdbcUrl jdbc:mysql://localhost/database
>   UserName YYYY
>   Password XXXX
>   JtaManaged true
> </Resource>
> {code}
> Start tomee.
> You will see some warnings in the log like this.
> [main] INFO  unknown.jul.logger - Creating Resource(id=repairDataSource)
> [main] WARN  unknown.jul.logger - Property "JdbcUrl" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "UserName" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "Password" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "PasswordCipher" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "ConnectionProperties" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "DefaultAutoCommit" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "DefaultReadOnly" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "InitialSize" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "MaxActive" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "MaxIdle" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "MinIdle" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "ValidationQuery" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "TestOnBorrow" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "TestOnReturn" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "TestWhileIdle" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "NumTestsPerEvictionRun" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "PoolPreparedStatements" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "MaxOpenPreparedStatements" not supported by "repairDataSource"
> WARN  unknown.jul.logger - Property "AccessToUnderlyingConnectionAllowed" not supported by "repairDataSource" 
> The DataSoruce itself can be discovered via JNDI in the application but is not configured probably.
> A usage results in a SQL Exception, saying user 'sa' has no access rights in the database. 
> It seams that the configuration parameters are ignored and some default values from HSQLDB are used.
> Using the "JdbcDriver com.mysql.jdbc.Driver" solves the issue, but this driver does not support any XA abilities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)