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

Richard Zowalla resolved TOMEE-1337.
------------------------------------
    Resolution: Auto Closed

Hi there!

We wanted to reach out and let you know that we're currently working on 
cleaning up open issues in Jira that specifically impact unsupported versions, 
including 1.7.x, 7.0.x, and 7.1.x.

If you had previously reported this issue on one of these unsupported versions, 
we kindly ask you to check if the problem still persists and can be reproduced 
on a supported version such as 8.0.x or 9.0.x. If you find that it is indeed 
reproducible on a supported version, you're more than welcome to re-open this 
issue.

Thanks!


> 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: Major
>         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
(v8.20.10#820010)

Reply via email to