JBoss Server Integration Verification

Check the JBoss log at JBOSS_HOME/standalone/log/server.log or in standalone.bat to confirm whether your application uses the Delinea JDBC Proxy Driver.

Verifying a Non-XA DataSource Connection

If your application uses the Delinea Proxy Driver with a Non-XA DataSource, the log displays the following sequence:

  • DelineaDriver: Driver register successfully
  • DelineaDriver: Loading the property file of DelineaDriver
  • DelineaDriverHelper: Driver configuration read successfully
  • DelineaDriver: DB credential fetched successfully from Secret Server

These log entries confirm that the JDBC Proxy Driver was loaded successfully, the driver is reading its configuration from the DelineaDriver.properties file, and database credentials are being successfully fetched.

Verifying an XA DataSource Connection

If your application uses the Delinea Proxy Driver with an XA DataSource, the log displays the following sequence:

  • DelineaXADataSource: getXAConnection()
  • DelineaDriverHelper: Inside DelineaDriverHelperinit
  • DelineaDriverHelper: Driver configuration read successfully
  • DelineaDriverHelper: Inside getSSCredential
  • CommonDelineaDataSource: DB credential fetched successfully from Server

These log entries confirm that the XA data source logic is being executed, the JDBC Proxy Driver is initializing correctly, the driver is able to read its configuration, and database credentials are being successfully fetched.

JBoss server.log File Errors

The following are solutions for common errors in the server.log file.

  • DelineaDriver: Could not register the driver.

    Solution: Check all parameters in the DelineaDriver.properties file.

  • DelineaDriver: Unable to read the DelineaDriver.properties file.

    Solution: Verify that the file is named DelineaDriver.properties and that it is present in the JBOSS_HOME/modules/com/delinea/main directory.

  • DelineaDriver: URL is not valid. It must start with jdbc:delinea.

    Solution: Check the connection string in standalone.xml.

    • For Non-XA DataSources, the <connection-url> must start with jdbc:delinea:. For example, for SQL Server: jdbc:delinea:sqlserver://localhost:1433;databaseName=onlinebookstore.
    • For XA DataSources, verify that the URL property contains a valid database connection URL.

  • SecretServer - getSecret: error getting secret.

    Solution: Verify the secret ID in your DataSource configuration. For Non-XA, check the delinea_secretId connection property. For XA, check the delinea_secretId xa-datasource-property.

  • Failed to get connection java.sql.SQLException: no suitable driver found.

    Solution: Check whether the JBOSS_HOME/modules/com/mysql/main folder contains the native driver JAR (e.g., mysql-connector-java-8.0.28.jar).

You can change only the isLogging and logLevel parameters in the DelineaDriver.properties file manually. You must run SetupUtility.jar to change other parameters (such as URL and identity), or the proxy driver will not work as expected.