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

Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set #443

Closed
4 tasks done
jameskleeh opened this issue Mar 18, 2020 · 1 comment
Closed
4 tasks done

Comments

@jameskleeh
Copy link
Contributor

This application ran OK with Micronaut Data 1.0.0 and now fails to start with 1.0.1

Task List

  • Steps to reproduce provided
  • Stacktrace (if present) provided
  • Example that reproduces the problem uploaded to Github
  • Full description of the issue provided (see below)

Steps to Reproduce

  1. Clone https://github.com/JasonTypesCodes/micronaut-json-issue
  2. cd jhipster-micronaut
  3. ./mvnw clean exec:exec

Expected Behaviour

The app runs

Actual Behaviour

The application fails to start with:

Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set
        at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
        at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
        at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
        at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:101)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
@jameskleeh
Copy link
Contributor Author

Closing this because it seems the app had micronaut-data-hibernate-jpa and micronaut-data-jdbc set to 1.0.0 so likely the other transitive modules were updated to 1.0.1 causing a conflict. I removed the set versions and it is working OK.

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