Agroal as Default DataSource

[pmm]

We are trying out Agroal and could not yet get it working as a default DataSource.

We added the extension

<extension module="org.wildfly.extension.datasources-agroal"/>

and then replaced the default datasources subsystem configuration with what we believe is the Agroal equivalent

<subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0">

  <datasource name="ExampleDS" jndi-name="java:jboss/datasources/ExampleDS">

      <connection-factory driver="h2" url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE" username="sa" password="sa">

      </connection-factory>

      <connection-pool max-size="30"/>

  </datasource>

  <drivers>

    <driver name="h2" module="com.h2database.h2" class="org.h2.Driver"/>

  </drivers>

</subsystem>

We kept the same JDNI name upon lookup of the data source we get:

Caused by: javax.naming.NameNotFoundException: DefaultDataSource -- service jboss.naming.context.java.module."transaction-query-timeout-test-0.1.0-SNAPSHOT"."transaction-query-timeout-test-0.1.0-SNAPSHOT".DefaultDataSource

  at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)

  at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:239)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)

  at javax.naming.InitialContext.lookup(InitialContext.java:417)

  at javax.naming.InitialContext.lookup(InitialContext.java:417)

  at com.github.marschall.transactionquerytimeouttest.QueryTimeoutBean.getQueryTimeout(QueryTimeoutBean.java:29)

  ... 110 more

Is there some additional configuration that we missed?

[simkam]

Hi,

currently it is datasources subsystem that is responsible for DefaultDataSource binding. Workaround is to add empty datasources subsystem to configuration.

<subsystem xmlns="urn:jboss:domain:datasources:5.0">

</subsystem>

I created [WFLY-11221] Agroal datasource cannot be used as DefaultDataSource without connector subsystem - JBoss Issue Tracker  for fix.

[rcd]

If you're using WF 14, I would recommend against using Agroal. I switched to it in a couple applications and had to revert to the old datasources subsystem due to a nasty bug in the version of Agroal shipped in WF 14. See WFLY-11037 and AG-94. The issue should be fixed in WF 15, or you could try upgrading the Agroal JARs in 14 by hand, I suppose.

[pmm]

simkam  wrote:

Hi,

currently it is datasources subsystem that is responsible for DefaultDataSource binding. Workaround is to add empty datasources subsystem to configuration.

<subsystem xmlns="urn:jboss:domain:datasources:5.0">

</subsystem>

I created [WFLY-11221] Agroal datasource cannot be used as DefaultDataSource without connector subsystem - JBoss Issue Tracker  for fix.

Awesome, thank you.

[pmm]

rcd  wrote:

If you're using WF 14, I would recommend against using Agroal. I switched to it in a couple applications and had to revert to the old datasources subsystem due to a nasty bug in the version of Agroal shipped in WF 14. See WFLY-11037 and AG-94. The issue should be fixed in WF 15, or you could try upgrading the Agroal JARs in 14 by hand, I suppose.

We have no immediate plans for production use of Agroal. We're just having a first look and perform some testing. We understand it is in active development and more in a "preview" mode.