Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9227

XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 10.1.0.Final
    • JCA, Web Console
    • None
    • Hide
      • Setup an oracle database, but it might be reproducible with other DB's as well
      • Move the DB connection details into a properties file
      • If necessary, install JDBC module
      • Setup the DB connection in standalone xml, using expressions as outlined above.
      • Start the server with the properties file referenced in standalone mode
      • Login to the admin console and navigate to subsystems > datasources > xa-datasources
      Show
      Setup an oracle database, but it might be reproducible with other DB's as well Move the DB connection details into a properties file If necessary, install JDBC module Setup the DB connection in standalone xml, using expressions as outlined above. Start the server with the properties file referenced in standalone mode Login to the admin console and navigate to subsystems > datasources > xa-datasources

      I expected the this to work, but I does not seem to:

      GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
      	<subsystem xmlns="urn:jboss:domain:datasources:4.0">
      		<datasources>
      			<xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
      				<xa-datasource-property name="URL">
      					${source.db.url:undefined}
      				</xa-datasource-property>
      				<driver>OracleJDBCDriver</driver>
      				<xa-pool>
      					<min-pool-size>0</min-pool-size>
      					<max-pool-size>10</max-pool-size>
      					<is-same-rm-override>false</is-same-rm-override>
      					<no-tx-separate-pools>true</no-tx-separate-pools>
      				</xa-pool>
      				<security>
      					<user-name>${source.db.user:user}</user-name>
      					<password>${source.db.password:password}</password>
      				</security>
      				<recovery no-recovery="true"/>
      				<validation>
      					<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
      					<stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
      					<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
      				</validation>
      			</xa-datasource>
      		</datasources>
      		<drivers>
      			<driver name="h2" module="com.h2database.h2">
      				<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
      			</driver>
      			<driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
      				<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
      			</driver>
      		</drivers>
      	</subsystem>
      AND a /full/path/to/file.properties file fitting a database connection, containing
      	source.db.enabled=true
      	source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
      	source.db.user=USER
      	source.db.password=PASSWORD
      WHEN the server is started with --properties=/full/path/to/file.properties
      THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
      

              hpehl@redhat.com Harald Pehl
              marius.schmidt Marius Schmidt (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: