[jboss-jira] [JBoss JIRA] (WFLY-4072) Unable to Enable JTA for a Datasource

[Stefano Maestri (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025334#comment-13025334 ] 

Stefano Maestri commented on WFLY-4072:
---------------------------------------

Could you provide me some more context please.
Attach your configuration (standalone/domain.xml should be fine) and how are you trying to enable JTA (via cli/webconsole whatever?)


> Unable to Enable JTA for a Datasource
> -------------------------------------
>
>                 Key: WFLY-4072
>                 URL: https://issues.jboss.org/browse/WFLY-4072
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>    Affects Versions: 8.1.0.Final
>         Environment: Windows 7
> Java 8u25
> WildFly 8.1.0.Final
>            Reporter: shinzey shinzey
>            Assignee: Stefano Maestri
>            Priority: Critical
>              Labels: Datasource, JTA, ejb, wildfly
>
> Whenever trying to enable JTA, the following error is reported:
> Unknown error
> Unexpected HTTP response: 500
> Request
> {
>     "name" => "test",
>     "user-name" => "test",
>     "password" => "test",
>     "security-domain" => "",
>     "jndi-name" => "java:/datasource/test",
>     "transaction-isolation" => "TRANSACTION_READ_COMMITTED",
>     "new-connection-sql" => "",
>     "connection-url" => "jdbc:derby://localhost:1527/test",
>     "driver-class" => "org.apache.derby.jdbc.ClientDriver",
>     "jta" => true,
>     "pool-name" => "",
>     "use-ccm" => false,
>     "datasource-class" => "",
>     "valid-connection-checker-class-name" => "",
>     "check-valid-connection-sql" => "",
>     "background-validation" => false,
>     "background-validation-millis" => -1L,
>     "validate-on-match" => false,
>     "stale-connection-checker-class-name" => "",
>     "exception-sorter-class-name" => "",
>     "prepared-statements-cache-size" => -1L,
>     "share-prepared-statements" => false,
>     "enabled" => false,
>     "driver-name" => "Derby_org.apache.derby.jdbc.ClientDriver_10_10",
>     "operation" => "enable",
>     "address" => [
>         ("subsystem" => "datasources"),
>         ("data-source" => "test")
>     ]
> }
> Response
> Internal Server Error
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014750: Operation handler failed to complete",
>     "rolled-back" => true
> }
> Due to this issue, EJB's transaction management does not work. I tested the same database on GlassFish and JTA works fine.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)