Cannot run the jmix-commercial-addons-demo-2.5.1?

C:\Users\james.jdks\corretto-19.0.2\bin\java.exe -Dvaadin.copilot.pluginDotFilePath=C:\swdev\jmix-commercial-addons-demo-2.5.1.idea.copilot-plugin “-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2024.3.5\lib\idea_rt.jar=56185” -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 @C:\Users\james\AppData\Local\Temp\idea_arg_file1359647267 com.company.demo.JmixCommercialAddonsDemo2Application

. ____ _ __ _ _
/\ / __ _ () __ __ _ \ \ \
( ( )_
_ | '_ | '| | ’ / ` | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
’ |
| .__|| ||| |_, | / / / /
=========|
|==============|/=////

:: Spring Boot :: (v3.4.4)

2025-05-26T12:06:23.834+08:00 INFO 29880 — [ main] c.d.JmixCommercialAddonsDemo2Application : Starting JmixCommercialAddonsDemo2Application using Java 19.0.2 with PID 29880 (C:\swdev\jmix-commercial-addons-demo-2.5.1\build\classes\java\main started by james in C:\swdev\jmix-commercial-addons-demo-2.5.1)
2025-05-26T12:06:23.837+08:00 INFO 29880 — [ main] c.d.JmixCommercialAddonsDemo2Application : No active profile set, falling back to 1 default profile: “default”
2025-05-26T12:06:25.302+08:00 WARN 29880 — [ main] o.s.c.annotation.AnnotationTypeMapping : Support for convention-based annotation attribute overrides is deprecated and will be removed in Spring Framework 7.0. Please annotate the following attributes in @io.jmix.webdavrest.annotation.WebdavControllerAdvice with appropriate @AliasFor declarations: [assignableTypes, annotations, basePackageClasses, basePackages]
2025-05-26T12:06:26.300+08:00 INFO 29880 — [ main] io.jmix.core.JmixModulesProcessor : Using Jmix modules: [io.jmix.core, io.jmix.security, io.jmix.flowui, io.jmix.securityflowui, io.jmix.data, io.jmix.bpm, io.jmix.bpmflowui, io.jmix.businesscalendar, io.jmix.businesscalendarflowui, io.jmix.datatools, io.jmix.datatoolsflowui, io.jmix.eclipselink, io.jmix.flowuidata, io.jmix.gridexportflowui, io.jmix.kanbanflowui, io.jmix.localfs, io.jmix.maps, io.jmix.mapsflowui, io.jmix.notifications, io.jmix.notificationsflowui, io.jmix.securitydata, io.jmix.uiconstraints, io.jmix.webdav, io.jmix.webdavflowui, io.jmix.webdavrest, com.company.demo]
2025-05-26T12:06:26.327+08:00 WARN 29880 — [ main] o.s.c.a.ConfigurationClassPostProcessor : Cannot enhance @Configuration bean definition ‘io.jmix.core.CoreConfiguration’ since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as ‘static’ and/or marking the containing configuration class as ‘proxyBeanMethods=false’.
2025-05-26T12:06:26.710+08:00 WARN 29880 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_EntityDetector’ of type [io.jmix.core.impl.scanning.EntityDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [methodValidationPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-26T12:06:26.710+08:00 WARN 29880 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_EnumDetector’ of type [io.jmix.core.impl.scanning.EnumDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [methodValidationPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-26T12:06:26.710+08:00 WARN 29880 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_JpaConverterDetector’ of type [io.jmix.core.impl.scanning.JpaConverterDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [methodValidationPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-26T12:06:26.711+08:00 WARN 29880 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_SpecificOperationAccessContextDetector’ of type [io.jmix.core.security.impl.SpecificOperationAccessContextDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [methodValidationPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-26T12:06:26.711+08:00 WARN 29880 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘sec_ResourceRoleDetector’ of type [io.jmix.security.impl.role.provider.ResourceRoleDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [methodValidationPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-26T12:06:26.711+08:00 WARN 29880 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘sec_RowLevelRoleDetector’ of type [io.jmix.security.impl.role.provider.RowLevelRoleDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [methodValidationPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

Process finished with exit code 1

image
The jmix-commercial-addons-demo-2.5.1 is came from there as in the screenshot.

Hi @hon.jan

The warnings in the log do not prevent the application from running properly.

Please make sure your trial add-ons are not expired (28 days after requesting the trial). If that’s the case, send us an email at info@jmix.io so we could extend the trial.

Regards,
Konstantin

I already set the email ya :smile:

Task :bootRun

. ____ _ __ _ _
/\ / __ _ () __ __ _ \ \ \
( ( )_
_ | '_ | '| | ’ / ` | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
’ |
| .__|| ||| |_, | / / / /
=========|
|==============|/=////
:: Spring Boot :: (v2.7.18)

2025-05-27 07:26:20.890 INFO 24532 — [ main] com.company.demo.DemoApplication : Starting DemoApplication using Java 17.0.9 on LAPTOP-UEE67MB4 with PID 24532 (C:\Users\james\Downloads\jmix-enterprise-trial (1)\jmix-commercial-addons-demo-1.6.2\build\classes\java\main started by james in C:\Users\james\Downloads\jmix-enterprise-trial (1)\jmix-commercial-addons-demo-1.6.2)
2025-05-27 07:26:20.893 INFO 24532 — [ main] com.company.demo.DemoApplication : No active profile set, falling back to 1 default profile: “default”
2025-05-27 07:26:23.196 INFO 24532 — [ main] io.jmix.core.JmixModulesProcessor : Using Jmix modules: [io.jmix.core, io.jmix.security, io.jmix.ui, io.jmix.securityui, io.jmix.data, io.jmix.bpm, io.jmix.bpmui, io.jmix.businesscalendar, io.jmix.businesscalendarui, io.jmix.datatools, io.jmix.gridexportui, io.jmix.datatoolsui, io.jmix.eclipselink, io.jmix.localfs, io.jmix.maps, io.jmix.mapsui, io.jmix.notifications, io.jmix.notificationsui, io.jmix.securitydata, io.jmix.uidata, io.jmix.webdav, io.jmix.webdavrest, io.jmix.webdavui, com.company.demo]
2025-05-27 07:26:23.201 INFO 24532 — [ main] o.s.c.a.ConfigurationClassPostProcessor : Cannot enhance @Configuration bean definition ‘com.vaadin.spring.VaadinConfiguration’ since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as ‘static’.
2025-05-27 07:26:23.417 INFO 24532 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_JpaConverterDetector’ of type [io.jmix.core.impl.scanning.JpaConverterDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2025-05-27 07:26:23.418 INFO 24532 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_EntityDetector’ of type [io.jmix.core.impl.scanning.EntityDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2025-05-27 07:26:23.418 INFO 24532 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘core_SpecificOperationAccessContextDetector’ of type [io.jmix.core.security.impl.SpecificOperationAccessContextDetector] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

Task :bootRun FAILED

Execution failed for task ‘:bootRun’.

Process ‘command ‘C:\Users\james.jdks\liberica-17.0.9\bin\java.exe’’ finished with non-zero exit value 1

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

It’s still same problem after extend the enterprise trial. Why?

Hi @hon.jan

We’ve sent you an email with the new subscription key that provides access to all commercial add-ons for a month.

Please enter it in your Studio:

  • Jmix tool window → SettingsAccount Information
  • Click Remove Subscription
  • Click Enter License Key and enter the received key

Studio will use this subscription and also write the key to your ~/.gradle/gradle.properties file to provide access to the premium add-ons repository to Gradle.

When the new trial subscription expires, you should remove it from Studio and add the old key or assign it to your account on the Jmix website as described in the docs: Subscription Management.

To evaluate commercial add-ons, please clone the following demo project: GitHub - jmix-framework/jmix-commercial-addons-demo-2: Jmix Commercial Add-ons Demo. It can be opened in IDE and launched after setting up the Enterprise subscription in your Studio and Gradle.

Regards,
Konstantin