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

JavaHibernateMavenJpaSpring Boot

Java Problem Overview


I am trying run a spring-boot application which uses hibernate via spring-jpa, but i am getting this error:

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:104)
        at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:71)
        at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:205)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
        at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885)
        at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
        at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
        at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
        at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:398)
        at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
        at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:152)
        at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:336)
        at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:318)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1613)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1550)
        ... 21 more

my pom.xml file is this:

<parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>1.1.8.RELEASE</version>
</parent>

<dependencies>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
    </dependency>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-actuator</artifactId>
    </dependency>
	<dependency>
	    <groupId>org.springframework.security</groupId>
	    <artifactId>spring-security-web</artifactId>
	   </dependency>
  	<dependency>
  		<groupId>org.springframework.security</groupId>
  		<artifactId>spring-security-config</artifactId>
  	</dependency>
	<dependency>
		<groupId>org.springframework.security</groupId>
		<artifactId>spring-security-taglibs</artifactId>
	</dependency>
	<dependency>
	    <groupId>org.springframework.boot</groupId>
	    <artifactId>spring-boot-starter-data-jpa</artifactId>
	</dependency>
	<dependency>
	    <groupId>commons-dbcp</groupId>
	    <artifactId>commons-dbcp</artifactId>
    </dependency>
</dependencies>

my hibernate configuration is that (the dialect configuration is in the last method from this class):

@Configuration
@EnableTransactionManagement
@ComponentScan({ "com.spring.app" })
public class HibernateConfig {
 
   @Bean
   public LocalSessionFactoryBean sessionFactory() {
      LocalSessionFactoryBean sessionFactory = new LocalSessionFactoryBean();
      
      sessionFactory.setDataSource(restDataSource());
      sessionFactory.setPackagesToScan(new String[] { "com.spring.app.model" });
      sessionFactory.setHibernateProperties(hibernateProperties());
 
      return sessionFactory;
   }
   
   @Bean
   public DataSource restDataSource() {
      BasicDataSource dataSource = new BasicDataSource();
      
      dataSource.setDriverClassName("org.postgresql.Driver");
      dataSource.setUrl("jdbc:postgresql://localhost:5432/teste?charSet=LATIN1");
      dataSource.setUsername("klebermo");
      dataSource.setPassword("123");
 
      return dataSource;
   }
 
   @Bean
   @Autowired
   public HibernateTransactionManager transactionManager(SessionFactory sessionFactory) {
      HibernateTransactionManager txManager = new HibernateTransactionManager();
      txManager.setSessionFactory(sessionFactory);
      return txManager;
   }
 
   @Bean
   public PersistenceExceptionTranslationPostProcessor exceptionTranslation() {
      return new PersistenceExceptionTranslationPostProcessor();
   }
 
   Properties hibernateProperties() {
      return new Properties() {
         /**
		 * 
		 */
		private static final long serialVersionUID = 1L;

		{
            setProperty("hibernate.hbm2ddl.auto", "create");
            setProperty("hibernate.show_sql", "false");
            setProperty("hibernate.dialect", "org.hibernate.dialect.PostgreSQLDialect");
         }
      };
   }
}

what I am doing wrong here?

Java Solutions


Solution 1 - Java

First remove all of your configuration Spring Boot will start it for you.

Make sure you have an application.properties in your classpath and add the following properties.

spring.datasource.url=jdbc:postgresql://localhost:5432/teste?charSet=LATIN1
spring.datasource.username=klebermo
spring.datasource.password=123

spring.jpa.database-platform=org.hibernate.dialect.PostgreSQLDialect
spring.jpa.show-sql=false
spring.jpa.hibernate.ddl-auto=create

If you really need access to a SessionFactory and that is basically for the same datasource, then you can do the following (which is also documented here although for XML, not JavaConfig).

@Configuration        
public class HibernateConfig {

    @Bean
    public HibernateJpaSessionFactoryBean sessionFactory(EntityManagerFactory emf) {
         HibernateJpaSessionFactoryBean factory = new HibernateJpaSessionFactoryBean();
         factory.setEntityManagerFactory(emf);
         return factory;
    }
}

That way you have both an EntityManagerFactory and a SessionFactory.

UPDATE: As of Hibernate 5 the SessionFactory actually extends the EntityManagerFactory. So to obtain a SessionFactory you can simply cast the EntityManagerFactory to it or use the unwrap method to get one.

public class SomeHibernateRepository {

  @PersistenceUnit
  private EntityManagerFactory emf;

  protected SessionFactory getSessionFactory() {
    return emf.unwrap(SessionFactory.class);
  }

}

Assuming you have a class with a main method with @EnableAutoConfiguration you don't need the @EnableTransactionManagement annotation, as that will be enabled by Spring Boot for you. A basic application class in the com.spring.app package should be enough.

@Configuration
@EnableAutoConfiguration
@ComponentScan
public class Application {


    public static void main(String[] args) throws Exception {
        SpringApplication.run(Application.class, args);
    }

} 

Something like that should be enough to have all your classes (including entities and Spring Data based repositories) detected.

UPDATE: These annotations can be replaced with a single @SpringBootApplication in more recent versions of Spring Boot.

@SpringBootApplication
public class Application {

    public static void main(String[] args) throws Exception {
        SpringApplication.run(Application.class, args);
    }
} 

I would also suggest removing the commons-dbcp dependency as that would allow Spring Boot to configure the faster and more robust HikariCP implementation.

Solution 2 - Java

I was facing a similar problem when starting up the application (using Spring Boot) with the database server down.

Hibernate can determine the correct dialect to use automatically, but in order to do this, it needs a live connection to the database.

Solution 3 - Java

add spring.jpa.properties.hibernate.dialect = org.hibernate.dialect.MySQLDialect in application.properties file

Solution 4 - Java

I got this error when my database was not created. After creating the DB manually, it worked fine.

Solution 5 - Java

I also faced a similar issue. But, it was due to the invalid password provided. Also, I would like to say your code seems to be old-style code using spring. You already mentioned that you are using spring boot, which means most of the things will be auto configured for you. hibernate dialect will be auto selected based on the DB driver available on the classpath along with valid credentials which can be used to test the connection properly. If there is any issue with the connection you will again face the same error. only 3 properties needed in application.properties

# Replace with your connection string
spring.datasource.url=jdbc:mysql://localhost:3306/pdb1

# Replace with your credentials
spring.datasource.username=root
spring.datasource.password=

Solution 6 - Java

I ran into the same problem and my issue was that the DB I was trying to connect to didn't exist.

I created the DB, verified the URL/connection string and reran and everything worked as expected.

Solution 7 - Java

Remove the redundant Hibernate Configuration

If you're using Spring Boot, you don't need to provide the JPA and Hibernate configuration explicitly, as Spring Boot can do that for you.

Add database configuration properties

In the application.properties Spring Boot configuration file, you have the add your database configuration properties:

spring.datasource.driverClassName = org.postgresql.Driver
spring.datasource.url = jdbc:postgresql://localhost:5432/teste
spring.datasource.username = klebermo
spring.datasource.password = 123

Add Hibernate specific properties

And, in the same application.properties configuration file, you can also set custom Hibernate properties:

# Log SQL statements
spring.jpa.show-sql = false

# Hibernate ddl auto for generating the database schema
spring.jpa.hibernate.ddl-auto = create

# Hibernate database Dialect
spring.jpa.properties.hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect

That's it!

Solution 8 - Java

I had same issue. adding this to the application.properties solved the issue:

spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQLDialect

Solution 9 - Java

In spring boot for jpa java config you need to extend JpaBaseConfiguration and implement it's abstract methods.

@Configuration
public class JpaConfig extends JpaBaseConfiguration {

    @Override
    protected AbstractJpaVendorAdapter createJpaVendorAdapter() {
        final HibernateJpaVendorAdapter vendorAdapter = new HibernateJpaVendorAdapter();
        return vendorAdapter;
    }

    @Override
    protected Map<String, Object> getVendorProperties() {
        Map<String, Object> properties = new HashMap<>();
        properties.put("hibernate.dialect", "org.hibernate.dialect.PostgreSQLDialect");
    }

}

Solution 10 - Java

The following are some of the reasons for the hibernate.dialect not set issue. Most of these exceptions are shown in the startup log which is finally followed by the mentioned issue.

Example: In Spring boot app with Postgres DB

  1. Check if the database is actually installed and its server is started.

  • org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
  • java.net.ConnectException: Connection refused: connect
  • org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
  1. Check if the database name is correctly mentioned.

  • org.postgresql.util.PSQLException: FATAL: database "foo" does not exist

In application.properties file,

    spring.datasource.url = jdbc:postgresql://localhost:5432/foo

but foo didn't exist. So I created the database from pgAdmin for postgres

    CREATE DATABASE foo;

3. Check if the host name and server port is accessible.

  • org.postgresql.util.PSQLException: Connection to localhost:5431 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
  • java.net.ConnectException: Connection refused: connect
  1. Check if the database credentials are correct.

  • as @Pankaj mentioned

  • org.postgresql.util.PSQLException: FATAL: password authentication failed for user "postgres"

    spring.datasource.username= {DB USERNAME HERE}

    spring.datasource.password= {DB PASSWORD HERE}

Solution 11 - Java

Make sure your application.properties has all correct info: (I changed my db port from 8889 to 3306 it worked)

 db.url: jdbc:mysql://localhost:3306/test

Solution 12 - Java

this is happening because your code is not bale to connect the database. Make sure you have mysql driver and username, password correct.

Solution 13 - Java

In my case the user could not connect to the database. If will have same issue if the log contains a warning just before the exception:

WARN HHH000342: Could not obtain connection to query metadata : Login failed for user 'my_user'.

Solution 14 - Java

Make sure you have your database in your pom like OP did. That was my problem.

Solution 15 - Java

My problem was that embedded database was already connected. close connection

Solution 16 - Java

I got this issue when Eclipse was unable to find the JDBC driver. Had to do a gradle refresh from the eclipse to get this work.

Solution 17 - Java

It turns out there is no one mentioning set spring.jpa.database=mysql in application.properties file, if you use Spring JPA. This is the simplest answer to me and I want to share in this question.

Solution 18 - Java

If you are using this line:

sessionFactory.getHibernateProperties().put("hibernate.dialect", env.getProperty("hibernate.dialect"));

make sure that env.getProperty("hibernate.dialect") is not null.

Solution 19 - Java

> Same but in a JBoss WildFly AS.

Solved with properties in my META-INF/persistence.xml

<properties>
			<property name="hibernate.transaction.jta.platform"
				value="org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform" />
			<property name="spring.jpa.database-platform" value="org.hibernate.dialect.PostgreSQLDialect" />
			<property name="spring.jpa.show-sql" value="false" />
</properties>

Solution 20 - Java

For those working with AWS MySQL RDS, it may occur when you are unable to connect to the database. Go to AWS Security Groups setting for MySQL RDS and edit the inbound IP rule by refreshing MyIP.

I faced this issue and doing above got the problem fixed for me.

Solution 21 - Java

I also had this problem. In my case it was because of no grants were assigned to MySQL user. Assigning grants to MySQL user which my app uses resolved the issue:

grant select, insert, delete, update on my_db.* to 'my_user'@'%';

Solution 22 - Java

I had the same issue and after debugging it turns out that Spring application.properties had wrong IP address for DB server

spring.datasource.url=jdbc:oracle:thin:@WRONG:1521/DEV

Solution 23 - Java

Adding spring.jpa.database-platform=org.hibernate.dialect.MariaDB53Dialect to my properties file worked for me.

PS: i'm using MariaDB

Solution 24 - Java

I reproduced this error message in the following three cases:

  • There does not exist database user with username written in application.properties file or persistence.properties file or, as in your case, in HibernateConfig file
  • The deployed database has that user but user is identified by different password than that in one of above files
  • The database has that user and the passwords match but that user does not have all privileges needed to accomplish all database tasks that your spring-boot app does

The obvious solution is to create new database user with the same username and password as in the spring-boot app or change username and password in your spring-boot app files to match an existing database user and grant sufficient privileges to that database user. In case of MySQL database this can be done as shown below:

mysql -u root -p 
>CREATE USER 'theuser'@'localhost' IDENTIFIED BY 'thepassword';
>GRANT ALL ON *.* to theuser@localhost IDENTIFIED BY 'thepassword';
>FLUSH PRIVILEGES;

Obviously there are similar commands in Postgresql but I haven't tested if in case of Postgresql this error message can be reproduced in these three cases.

Solution 25 - Java

I had the same issue and it was caused by being unable to connect to the database instance. Look for hibernate error HHH000342 in the log above that error, it should give you an idea to where the db connection is failing (incorrect username/pass, url, etc.)

Solution 26 - Java

This happened to me because I hadn't added the conf.configure(); before beginning the session:

Configuration conf = new Configuration();
conf.configure();

Solution 27 - Java

Make sure that you have enter valid detail in application.properties and whether your database server is available. As a example when you are connecting with MySQL check whether XAMPP is running properly.

Solution 28 - Java

I faced the same issue: The db I was trying to connect did not exist. I used jpa.database=default (which I guess means it will try to connect to the database and then auto select the dialect). Once I started the database, it worked fine without any change.

Solution 29 - Java

I had the same error after using the hibernate code generation

https://www.mkyong.com/hibernate/how-to-generate-code-with-hibernate-tools/

then the hibernate.cfg.xml was created in /src/main/java but without the connection parameters after removing it - my problem was solved

Solution 30 - Java

I faced this issue due to Mysql 8.0.11 version reverting back to 5.7 solved for me

Solution 31 - Java

If the preceding error in log was this: "ERROR - HikariPool-1 - jdbcUrl is required with driverClassName" then the solution is to rewrite "url" to "jdbc-url" according to this: https://stackoverflow.com/questions/33323837/database-application-yml-for-spring-boot-from-applications-properties

Solution 32 - Java

I had the same Error,

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

in my case the WAR had application.properties inside that pointed to development server
where external application.properties was pointing to the right DB server.

make sure you don't have any other application.properties in the classpath / jars...

Solution 33 - Java

In my case, the root cause of this exception comes from using an old version mysql-connector and I had this error :

unable to load authentication plugin 'caching_sha2_password'. mysql

Adding this line to the mysql server configuration file (my.cnf or my.ini) fix this issue :

default_authentication_plugin=mysql_native_password

Solution 34 - Java

As a more descriptive answer


To fix the issue which is related to connecting to the database:

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) ~[hibernate-core-5.4.8.Final.jar:5.4.8.Final]
	at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54) ~[hibernate-core-5.4.8.Final.jar:5.4.8.Final]
	at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137) ~[hibernate-core-5.4.8.Final.jar:5.4.8.Final]
	at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35) ~[hibernate-core-5.4.8.Final.jar:5.4.8.Final]
	at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:101) ~[hibernate-core-5.4.8.Final.jar:5.4.8.Final]
	at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263) ~[hibernate-core-5.4.8.Final.jar:5.4.8.Final]
	... 38 common frames omitted

everything you need to do is:

  1. To choose specific Data Source configuration option related to the required database (which you are using inside your application.properties file), e.g. you have spring.datasource.platform=postgres:

enter image description here

  1. To avoid "FATAL: database "testDb" does not exist" while connecting:

enter image description here

using PgAdmin needs to create manually the database (if you are using the development platform for PostgreSQL):

enter image description here

based on your property inside application.properties file:

spring.datasource.url=jdbc:postgresql://localhost:5432/testDb

3) Configure remaining settings:

  • spring.datasource.url=jdbc:postgresql://localhost:5432/testDb
  • spring.datasource.username=postgres
  • spring.datasource.password=your_password

based on your application.properties file:

enter image description here

  1. Click "Test Connection" and "Apply".

Solution 35 - Java

For me, The problem solved by doing as following :

Right click on Entities on Persistence window and select related data source

Solution 36 - Java

Checking the code (HibernateJpaVendorAdapter && JdbcEnvironmentInitiator), the fallback looks like this:

  • if spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults is true then the dialect is obtained from the db.
    • Else, if spring.jpa.database-platform is set, get the dialect from there
      • Else, if spring.jpa.database is set, get a default hardocded dialect mapped in HibernateJpaVendorAdapter

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionKleber MotaView Question on Stackoverflow
Solution 1 - JavaM. DeinumView Answer on Stackoverflow
Solution 2 - JavamhnagaokaView Answer on Stackoverflow
Solution 3 - JavaalpineView Answer on Stackoverflow
Solution 4 - JavaACVView Answer on Stackoverflow
Solution 5 - JavaPankajView Answer on Stackoverflow
Solution 6 - JavaEric B.View Answer on Stackoverflow
Solution 7 - JavaVlad MihalceaView Answer on Stackoverflow
Solution 8 - JavaArthur KazemiView Answer on Stackoverflow
Solution 9 - JavaYaroslavView Answer on Stackoverflow
Solution 10 - JavaabitcodeView Answer on Stackoverflow
Solution 11 - JavaVikram SView Answer on Stackoverflow
Solution 12 - Javauser7169604View Answer on Stackoverflow
Solution 13 - JavazbigView Answer on Stackoverflow
Solution 14 - Javaobesechicken13View Answer on Stackoverflow
Solution 15 - Javadoesnt_matterView Answer on Stackoverflow
Solution 16 - JavaKannan RamamoorthyView Answer on Stackoverflow
Solution 17 - JavaChayne P. S.View Answer on Stackoverflow
Solution 18 - JavazygimantusView Answer on Stackoverflow
Solution 19 - JavaAlejandro Teixeira MuñozView Answer on Stackoverflow
Solution 20 - JavaAjiteshView Answer on Stackoverflow
Solution 21 - JavaYamashiro RionView Answer on Stackoverflow
Solution 22 - JavaJavaSheriffView Answer on Stackoverflow
Solution 23 - JavaJoel MataView Answer on Stackoverflow
Solution 24 - JavaVeli-Matti SorvalaView Answer on Stackoverflow
Solution 25 - JavaFaroukView Answer on Stackoverflow
Solution 26 - JavadianaView Answer on Stackoverflow
Solution 27 - JavaLahiru GamageView Answer on Stackoverflow
Solution 28 - JavaAvishekh TewariView Answer on Stackoverflow
Solution 29 - JavaRMagenView Answer on Stackoverflow
Solution 30 - JavaGautam YadavView Answer on Stackoverflow
Solution 31 - JavaJanBrusView Answer on Stackoverflow
Solution 32 - JavaJavaSheriffView Answer on Stackoverflow
Solution 33 - JavaDimitriView Answer on Stackoverflow
Solution 34 - Javainvzbl3View Answer on Stackoverflow
Solution 35 - JavaTohid MakariView Answer on Stackoverflow
Solution 36 - JavaWhimusicalView Answer on Stackoverflow