Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment fails due to JDBC Dialect Configuration issue #24

Open
peter-paperdog opened this issue Jun 16, 2024 · 0 comments
Open

Deployment fails due to JDBC Dialect Configuration issue #24

peter-paperdog opened this issue Jun 16, 2024 · 0 comments

Comments

@peter-paperdog
Copy link

Hi,

I am encountering an issue with the deployment of dcm4chee-arc-ear-5.32.0-psql.ear on the Wildfly server running. The error message indicates a problem with determining the JDBC dialect due to missing JDBC metadata. Below is the detailed error message:

{"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"dcm4chee-arc-ear-5.32.0-psql.ear#dcm4chee-arc\".__FIRST_PHASE__" => "org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] due to: Unable to determine Dialect without JDBC metadata (please set 'jakarta.persistence.jdbc.url' for common cases or 'hibernate.dialect' when a custom Dialect implementation must be provided) Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] due to: Unable to determine Dialect without JDBC metadata (please set 'jakarta.persistence.jdbc.url' for common cases or 'hibernate.dialect' when a custom Dialect implementation must be provided) Caused by: org.hibernate.HibernateException: Unable to determine Dialect without JDBC metadata (please set 'jakarta.persistence.jdbc.url' for common cases or 'hibernate.dialect' when a custom Dialect implementation must be provided)"}}}

Could you please provide guidance on how to correctly configure the JDBC dialect for the deployment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant