InstantiationException ao rodar JPQL com SELECT new

Oi Vinicius,

Aparentemente não vi problemas no seu código.

Consegue postar aqui a exception completa?

Olá Rodrigo, sim claro.

Segue a stack trace completa retornada pelo Eclipse.

javax.persistence.PersistenceException: org.hibernate.query.sqm.sql.internal.InstantiationException: Error performing dynamic instantiation : br.com.jpaexample.shop.vo.SalesReportVo
    at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:166)
    at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:193)
    at org.hibernate.query.spi.AbstractQuery.list(AbstractQuery.java:1373)
    at org.hibernate.query.Query.getResultList(Query.java:131)
    at br.com.jpaexample.shop.dao.CustomerOrderDao.getSalesReport(CustomerOrderDao.java:60)
    at br.com.jpaexample.shop.tests.VoTest.main(VoTest.java:21)
Caused by: org.hibernate.query.sqm.sql.internal.InstantiationException: Error performing dynamic instantiation : br.com.jpaexample.shop.vo.SalesReportVo
    at org.hibernate.sql.results.graph.instantiation.internal.DynamicInstantiationAssemblerConstructorImpl.assemble(DynamicInstantiationAssemblerConstructorImpl.java:58)
    at org.hibernate.sql.results.internal.StandardRowReader.readRow(StandardRowReader.java:93)
    at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:66)
    at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:24)
    at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:228)
    at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:146)
    at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:74)
    at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.lambda$new$0(ConcreteSqmSelectQueryPlan.java:80)
    at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:248)
    at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:191)
    at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:513)
    at org.hibernate.query.spi.AbstractQuery.list(AbstractQuery.java:1364)
    ... 3 more
Caused by: java.lang.IllegalArgumentException: argument type mismatch
    at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:78)
    at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
    at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
    at org.hibernate.sql.results.graph.instantiation.internal.DynamicInstantiationAssemblerConstructorImpl.assemble(DynamicInstantiationAssemblerConstructorImpl.java:52)
    ... 14 more

Não sei se ajuda, mas eu debuguei o processo e percebi que o erro ocorre na classe Classe DynamicInstantiationAssemblerConstructorImpl do pacote package org.hibernate.sql.results.graph.instantiation.internal:

    @Override
    public R assemble(
            RowProcessingState rowProcessingState,
            JdbcValuesSourceProcessingOptions options) {
        final int numberOfArgs = argumentReaders.size();
        Object[] args = new Object[ numberOfArgs ];
        for ( int i = 0; i < numberOfArgs; i++ ) {
            args[i] = argumentReaders.get( i ).assemble( rowProcessingState, options );
        }

        try {
            return targetConstructor.newInstance( args );
        }
        catch (InvocationTargetException e) {
            throw new InstantiationException( "Error performing dynamic instantiation : " + targetConstructor.getDeclaringClass().getName(), e.getCause() );
        }
        catch (Exception e) {
            throw new InstantiationException( "Error performing dynamic instantiation : " + targetConstructor.getDeclaringClass().getName(), e );
        }
    }

Aí chama o targetConstructor.newInstance...

    @CallerSensitive
    @ForceInline // to ensure Reflection.getCallerClass optimization
    public T newInstance(Object ... initargs)
        throws InstantiationException, IllegalAccessException,
               IllegalArgumentException, InvocationTargetException
    {
        Class<?> caller = override ? null : Reflection.getCallerClass();
        return newInstanceWithCaller(initargs, !override, caller);
    }

Quando esse método acima devolve o newInstance, aí volta com essa Exception:

 (java.lang.IllegalArgumentException) java.lang.IllegalArgumentException: argument type mismatch

O problema foi esse então: argument type mismatch

Parece que essa consulta JPQL não está devolvendo os mesmos tipos de atributos que definidos no construtor do seu VO.

Para verificar, faça o seguinte teste e veja quais são os tipos que estão chegando:

public List<SalesReportVo> getSalesReport() {
        String jpql = "SELECT "
                + "product.name, "
                + "SUM(item.quantity), "
                + "MAX(t_order.dateOrder) "
                + "FROM CustomerOrder t_order "
                + "JOIN t_order.items item "
                + "JOIN item.product product "
                + "GROUP BY product.name, "
                + "item.quantity "
                + "ORDER BY item.quantity DESC ";

        List<Object[]> resultado = em.createQuery(jpql).getResultList();
    resultado.foreach(r -> {
        System.out.println(r[0]);
        System.out.println(r[1]);
        System.out.println(r[2]);
    });
    return null;
    }

Exatamente Rodrigo,

Não me liguei que no banco postgres eu tenho o field quantity como sendo um integer. E na classe VO defini como Long. Na minha cabeça, eu tinha que o integer, por ser supostamente menor, caberia no Long do Java. Bastou alterar na VO para int que funcionou perfeitamente.

Muito obrigado Mestre.