Datasource and Configuration Issues in Lasernet Keep

Updated on 29 May 2026
5 Minutes to read
Contributors

Article summary

Did you find this summary helpful?

Thank you for your feedback

Lasernet Keep will fail to start if the configuration of the database connection is incorrect or the application cannot connect to the configured database. In both cases, an exception is thrown, which typically ends with the following message:

Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set.

This article applies to standalone installations only and explains:

How to locate the database configuration, which may need updating.
How to diagnose and fix the root cause of the issue.

Database Configuration

The database configuration is in standalone.xml:

<datasource jndi-name="java:/PDM" pool-name="PDM" enabled="true" use-java-context="true" use-ccm="true">
    <connection-url>${dm.datasource.connection.url}</connection-url>
    <driver>${dm.datasource.driver}</driver>
    <pool>
        <min-pool-size>${dm.datasource.pool.min}</min-pool-size>
        <max-pool-size>${dm.datasource.pool.max}</max-pool-size>
        <prefill>false</prefill>
        <use-strict-min>false</use-strict-min>
        <flush-strategy>FailingConnectionOnly</flush-strategy>
    </pool>
    <security>
        <user-name>${dm.datasource.username}</user-name>
        <password>${dm.datasource.password}</password>
    </security>
    <validation>
        <check-valid-connection-sql>
            ${dm.datasource.connection.validator.sql}
        </check-valid-connection-sql>
        <validate-on-match>false</validate-on-match>
        <background-validation>true</background-validation>
        <background-validation-millis>20000</background-validation-millis>
    </validation>
</datasource>

The following sections are important:

connection-url: A connection string that includes the Keep database location.
security: Authentication details for the database user in Keep.

The values for properties in the connection-url and security sections are specified in the node.properties file.

You can locate the standalone.xml and node.properties files in: <installation_directory>\Wildfly-<version>\standalone\configuration. Replace <installation_directory> and <version> as appropriate. The path to <installation directory> varies depending on whether you chose the default or a custom installation path.

General Symptoms

A database configuration error will cause Keep to fail to deploy correctly at startup and generate a large volume of error logs. Look for the following symptoms:

Keep fails to deploy on startup: Navigating to the web frontend results in a 404 - Not Found error message.

Check the server logs: The server logs typically contain a large number of entries, such as:

service jboss.deployment.subunit."pdm_app_module.ear"."applicationservice-8.0.0-SNAPSHOT.jar".component.ClientApplicationServiceEJB.VIEW."com.efstech.pdm.applicationservice.ejb.se
ssion.ClientApplicationService".LOCAL (missing) dependents: [service jboss.deployment.subunit."pdm_app_module.ear"."applicationservice-8.0.0-SNAPSHOT.jar".component.ClientApplicationSer
viceEJB.START]

Just before the deployment failure errors (as above), there is a stack trace ending with the line:

Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set

Identify the Root Cause

When you have confirmed the general symptoms:

Search for a log entry containing the following text:

IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection

Look for associated errors in the logs, then review the relevant section to confirm the root cause and find a fix:
- SQL Server Errors
- Oracle Errors