Another Case of failed to startup LCDP.ai low code development platform backend on JetBrains IDEA

General
1

Today, one of our customer meet another issue when try to start our platform on JetBrains Idea, the error in the idea console shown as below

a881f504379644485a86689d284ad05
a881f504379644485a86689d284ad052194×563 104 KB

2ee44dad80d3a8fb6ab7eb4f2c3383c
2ee44dad80d3a8fb6ab7eb4f2c3383c2282×907 362 KB

And that’s the complete log for troubleshooting:

Usersmr-pengLibraryJavaJavaVirtualMachinescorretto-11.0(2).txt (94.7 KB)

Our customer confirmed that the postgresql server is running and can connect successfully using pgadmin as below

4f17fc0de664c78ebe122dd05178773
4f17fc0de664c78ebe122dd051787731574×930 114 KB

What’s the issue here?

2

After a remote meeting and troubleshooting, we have figure out together with customer that a global proxy was on, which caused the backend service can not connect to the postgresql server.

BTW: Which indicates that the above error message of


1 connections initialized for localhost/127.0.0.1:6379
04-18 19:35:33.281  INFO [isson-netty-2-2] org.redisson.connection.pool.ConnectionPool.lambda$createConnection$1 [ConnectionPool.java:158] 
1 connections initialized for localhost/127.0.0.1:6379
ERROR SqlExceptionHelper 尝试连线已失败。
04-18 19:35:42.449  INFO [           main] org.redisson.Version.logVersion [Version.java:41] 
Redisson 3.17.5
04-18 19:35:42.474  INFO [isson-netty-5-1] org.redisson.connection.pool.ConnectionPool.lambda$createConnection$1 [ConnectionPool.java:158] 
1 connections initialized for localhost/127.0.0.1:6379
04-18 19:35:42.474  INFO [isson-netty-5-2] org.redisson.connection.pool.ConnectionPool.lambda$createConnection$1 [ConnectionPool.java:158] 
1 connections initialized for localhost/127.0.0.1:6379
ERROR SqlExceptionHelper 尝试连线已失败。
04-18 19:35:45.887 ERROR [           main] org.springframework.boot.SpringApplication.reportFailure [SpringApplication.java:830] 
Application run failed

org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationProcessingFilterDeregistrationBean': Cannot resolve reference to bean 'authenticationProcessingFilter' while setting bean property 'filter'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationProcessingFilter': Cannot resolve reference to bean 'authenticationManager' while setting bean property 'authenticationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationManager': Cannot resolve reference to bean 'daoAuthenticationProvider' while setting constructor argument with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daoAuthenticationProvider': Cannot resolve reference to bean 'userDetailsService' while setting bean property 'userDetailsService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userDetailsService': Unsatisfied dependency expressed through method 'setTargetDatastore' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateDatastore': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.grails.orm.hibernate.HibernateDatastore]: Constructor threw exception; nested exception is org.hibernate.exception.JDBCConnectionException: Unable to check JDBC Connection auto-commit in preparation for DDL execution
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:163)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:577)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:740)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:415)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
	at grails.boot.GrailsApp.run(GrailsApp.groovy:99)
	at grails.boot.GrailsApp.run(GrailsApp.groovy:485)
	at grails.boot.GrailsApp.run(GrailsApp.groovy:472)
	at tech.muyan.Application.main(Application.groovy:16)

Is caused by database not connectable, maybe because of

  1. Postgresql server is not start
  2. Postgresql server is not expose the port to backend service
  3. There’s some global proxy or firewall etc blocks backend service from connect to database server.

Hope this could be helpful for you.