[jboss-jira] [JBoss JIRA] (WFLY-5020) Server fails to start with transactions configured to be run with JDBCObject store

Stefano Maestri (JIRA) issues at jboss.org
Mon Sep 28 09:50:01 EDT 2015


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

Stefano Maestri commented on WFLY-5020:
---------------------------------------

Hi,

I'm a bit puzzled by your module config. A correct deployment w/ module should have a module created in modules/system/layers/base directory w/ its jar and a module.xml definition. Then standalone config of datasource should looks like:

{code:java}
<datasource jta="false" jndi-name="java:jboss/datasources/jdbc-store" pool-name="JDBCPool" enabled="true" use-java-context="true">
			<connection-url>jdbc:sqlserver://mssql2014server:1433;DatabaseName=database1</connection-url>
			<driver>microsoft</driver>
			<security>
  				<user-name>username1</user-name>
  				<password>password1</password>
			</security>
		</datasource>
                <drivers>
                    <driver name="h2" module="com.h2database.h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
		    <driver name="microsoft" module="com.microsoft.sql"></driver>
                </drivers>
{code}

Please note definition of driver in xml pointing the created module. I can't see anything of this in your module configuration.
Anyway I've configured and tried exactly the above configuration and it works w/o problem.
Looking again in the code I can see jdbc-store isn't designed to work w/ hot deployed driver (BTW it's not a best practice in general), I thought it was pointed out in documentation, but quite frankly I haven't found it. Maybe something to improve in documentation, but it's a different area and issue is solved even for sql server and any other database using module configuration. So I'm closing again this issue. Feel free to open a documentation improvement issue pointing this comment.

regards
S.

> Server fails to start with transactions configured to be run with JDBCObject store
> ----------------------------------------------------------------------------------
>
>                 Key: WFLY-5020
>                 URL: https://issues.jboss.org/browse/WFLY-5020
>             Project: WildFly
>          Issue Type: Bug
>          Components: Transactions
>            Reporter: Hayk Hovsepyan
>            Assignee: Stefano Maestri
>            Priority: Blocker
>             Fix For: 10.0.0.Final
>
>         Attachments: server.log, server_module.log, standalone.xml, standalone_module.xml
>
>
> When you configure transactions subsystem for running with JDBCObject store, the app server fails to start because of a error below.
> Error message:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]): org.jboss.msc.service.CircularDependencyException: Container jboss-as has a circular dependency: [service jboss.txn.ArjunaObjectStoreEnvironment, service jboss.txn.ArjunaRecoveryManager, service jboss.connector.transactionintegration, service jboss.rarepository, service jboss.data-source.java:jboss/datasources/jdbc-store, service jboss.data-source.reference-factory.JDBCPool, service jboss.naming.context.java.jboss.datasources.jdbc-store]
> {code}
> Datasource configuration is:
> {code}
> <datasource jta="false" jndi-name="java:jboss/datasources/jdbc-store" pool-name="JDBCPool" enabled="true" use-java-context="true">
> <connection-url>jdbc:sqlserver://mssql2014server:1433;DatabaseName=database1</connection-url>
> <driver>sqljdbc4.jar</driver>
> <security>
>   <user-name>username1</user-name>
>   <password>password1</password>
> </security>
> </datasource>
> {code}
> and the transaction config looks like this
> {code}
> <jdbc-store datasource-jndi-name="java:jboss/datasources/jdbc-store"/>
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list