initial build failing after generation #26375
Comments
|
JHipster has completed the sample check This check uses |
|
If I try to generate an app with your JDL, I get an error: |
|
I tried to simplify things to allow more info to fit. entity Order { I was able to roll back to Gadle 8.7 2024-06-12T08:49:09.619-07:00 ERROR 59314 --- [ restartedMain] j.LocalContainerEntityManagerFactoryBean : Failed to initialize JPA EntityManagerFactory: 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) Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: 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) Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. |
|
Can you please try with Node 20 and see if you experience the same issues? |
|
Usually: Means that database is not reachable. |
|
Using Node 20.14.0:
The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. 2024-06-12T09:03:34.207-07:00 WARN 35663 --- [ restartedMain] o.h.e.j.e.i.JdbcEnvironmentInitiator : HHH000342: Could not obtain connection to query metadata java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(java.sql.SQLException, String)" because the return value of "org.hibernate.resource.transaction.backend.jdbc.internal.JdbcIsolationDelegate.sqlExceptionHelper()" is null 2024-06-12T09:03:34.209-07:00 ERROR 35663 --- [ restartedMain] j.LocalContainerEntityManagerFactoryBean : Failed to initialize JPA EntityManagerFactory: 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) Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: 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) Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. Using npm run services:up
[+] Running 3/3 Maybe a configuration step missing? |
|
Having services database/kafka running is a requirement. |
|
Gatling is indeed failing to generate with the provided sample. |
It's not clear if there an issue in generated application. |
Overview of the issue
I used the following JDL:
Using: OSX, JHipster 8.5, openjdk@21
I try to run ./gradlew and get the following:
Motivation for or Use Case
I cannot build or run the generated application
Reproduce the error
I ran the JDL, then ran ./gradlew
Related issues
I don't see it
Suggest a Fix
JHipster Version(s)
New generation using JHipster 8.5
JHipster configuration
JDL definitions
application { config { baseName orderWriterService applicationType microservice packageName com.plexus.order.writer buildTool gradle serverPort 8090 serviceDiscoveryType no authenticationType no databaseType sql prodDatabaseType mysql devDatabaseType mysql cacheProvider no enableHibernateCache false skipClient true skipServer false enableSwaggerCodegen false skipUserManagement true messageBroker kafka websocket false nativeLanguage en enableTranslation false languages [en] jhiPrefix plexus dtoSuffix DTO testFrameworks [cucumber, gatling] searchEngine false } entities Order }entity Order {
baseCurrencyCode String minlength(0) maxlength(3),
baseDiscountAmount BigDecimal min(0) max(100000),
baseDiscountInvoiced BigDecimal min(0) max(100000),
baseGrandTotal BigDecimal min(0) max(100000),
baseDiscountTaxCompensationAmount BigDecimal min(0) max(100000),
baseDiscountTaxCompensationInvoiced BigDecimal min(0) max(100000),
baseShippingAmount BigDecimal min(0) max(100000)
}
Entity configuration(s)
entityName.jsonfiles generated in the.jhipsterdirectoryBrowsers and Operating System
OSX: 14.3 M2 chipset
The text was updated successfully, but these errors were encountered: