Connecting Cassandra to JNDI in WildFly: A Guide for Integration with cassandra-jdbc-wrapper-4.11.0.jar

[Arjunguptha98]

Hi team,
I've developed this project and obtained the cassandra-jdbc-wrapper-4.11.0.jar. With this JAR, I've successfully executed a Java JDBC program. Currently, I'm attempting to establish a connection between Cassandra and JNDI (using WildFly). Could you provide guidance on achieving this use case if it's possible?

[maximevw]

Hello @Arjunguptha98,

I´m not sure to understand your question.
If you want to configure a JDBC datasource identified by a JNDI name in WildFly, there is nothing specific to do for this driver and you can configure the datasource as any JDBC datasource in Wildfly as explained in the reference documentation.

And you can refer to this page for driver and connection URL settings.

[Arjunguptha98]

Hi @maximevw
Thank you for your reply. I've obtained the JDBC URL for Cassandra. However, I'm uncertain about how to configure the Cassandra driver in standalone.xml and module.xml.

[maximevw]

Hello @Arjunguptha98

First of all, I will convert this to a discussion as your question is not an issue related to the JDBC driver. :)

I have no expertise with Wildfly, but based on the following sources (here and there), I think you should do something like this:

(UPDATED on base of the next comments)

1. Download the driver JAR.
2. Put the JAR in the folder {WildFlyDirectory}/modules/system/layers/base/com/ing/data/main and create a module.xml file in the same folder:

<module xmlns="urn:jboss:module:1.9" name="com.ing.data">
  <resources>
    <resource-root path="cassandra-jdbc-wrapper-4.11.0-bundle.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
    <module name="org.apache.logging.log4j.api"/>
  </dependencies>
</module>

3. In the standalone.xml file, locate the <subsystem>/<datasources> part and include the following datasource :

<datasource jndi-name="java:jboss/datasources/cassandraDS" pool-name="cassandraDS" enabled="true">
  <connection-url>{JDBC URL}</connection-url>
  <driver>cassandra</driver>
  <security user-name="{username}" password="{password}" />
  </security>
</datasource>

4. Then, also in standalone.xml, locate the tag <drivers> and put this inside:

<driver name="cassandra" module="com.ing.data">
  <driver-class>com.ing.data.cassandra.jdbc.CassandraDriver</driver-class>
</driver>

5. Reboot the Wildfly server.

There is no guarantee it works exactly like this, I just deduced that from various documentation found on the Internet and I never tested this.

I really encourage you to consult the WildFly Admin guide for further details on JDBC datasource configuration.

[Arjunguptha98]

Hi @maximevw. Thanks for the response.
I attempted to configure Cassandra with Wildfly following the provided steps. However, I encountered a dependency issue, as outlined below.

[maximevw]

@Arjunguptha98,

It seems it doesn't find the driver. At step 2, I think there is a mistake and the directory should be {WildFlyDirectory}/modules/system/layers/base/com/ing/data/main.

[Arjunguptha98]

Hi @maximevw .
Still getting same dependency issue

[maximevw]

@Arjunguptha98, I installed Wildfly 30.0.1.Final locally, without deploying any application. And I just configured the datasource as specified above. I just modified a little the configuration as following:

<datasource jndi-name="java:jboss/datasources/cassandraDS" pool-name="cassandraDS" enabled="true">
  <connection-url>{JDBC URL}</connection-url>
  <driver>cassandra</driver>
  <security user-name="{username}" password="{password}"/>
</datasource>

And it seems it works:

18:21:28,493 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.ing.data.cassandra.jdbc.CassandraDriver (version 4.11)
18:21:28,497 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = cassandra
...
18:21:29,009 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
18:21:29,016 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/cassandraDS]
...
18:21:29,282 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
18:21:29,285 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
18:21:29,286 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
18:21:29,288 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 30.0.1.Final (WildFly Core 22.0.2.Final) started in 3466ms - Started 288 of 530 services (318 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml

And in the admin console, if I test the connection, it's ok.

Ensure the driver "cassandra" is present in the section <drivers> (just under the section <datasource>, inside the section <datasources>).

[Arjunguptha98]

Thank you for your insightful feedback. The details you shared were instrumental in resolving the issues I encountered with the setup.

[Arjunguptha98]

Hi @maximevw
While trying test the connection of cassandraDS(Test Connection) from the UI. I am getting below WARN issue

[maximevw]

Hi @Arjunguptha98
I will check that as soon as possible (probably a conflict with another module also importing this class since the "missing" class is present in the driver jar). But I think this is not blocking. Perhaps, the driver will just fail to write its internal logs but in most cases it's not really important.
I let you look for the error message on the Internet on your own in the meantime.

[maximevw]

@Arjunguptha98
Adding this line into the <dependencies> tag of the module.xml file of the JDBC driver, the warning message above disappeared when I test the connection:

<module name="org.apache.logging.log4j.api"/>

So, the module.xml file becomes:

<module xmlns="urn:jboss:module:1.9" name="com.ing.data">
  <resources>
    <resource-root path="cassandra-jdbc-wrapper-4.11.0-bundle.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
    <module name="org.apache.logging.log4j.api"/>
  </dependencies>
</module>

I will update my original message #47 (comment) to have the clean procedure.