JBoss Server Integration Verification

Delinea Driver Logs

Check the JBoss JBOSS_HOME\ standalone\log\server.log or in standalone.bat to confirm whether your application uses the Delinea JDBC Proxy Driver. If your application uses the Delinea Proxy Driver, it will display the following log 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

JBoss server.log File Errors

The following are the solutions for errors that occur in the JBoss 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: Check that the name of the file is DelineaDriver.properties and make sure the parameter is present in the configuration file.

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

    Solution: Check the connection string in the Java application configuration file.

    If you use SQL Server, the URL must be jdbc:sqlserver:SSID://localhost:1433;databaseName=onlinebookstore. If you use the JDBC Proxy URL, it must be: jdbc:delinea:SSID:sqlserver://localhost:1433;databaseName=onlinebookstore.

  • SecretServer - getSecret: error getting secret.

    Solution: Check your Secret ID in the Java application configuration file. It should appear in front of the database username box.

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

    Solution: Check whether the JBOSS_HOME\modules\com\mysql\main folder contains the driver mysql-connector-java-8.0.28.jar

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