not eligible for auto-proxying

2023-08-23 12:18:51.818 INFO 181806 [ main] egate$BeanPostProcessorChecker Bean 'lock4j-com.baomidou.lock.spring.boot.autoconfigure.Lock4jProperties' of type [com.baomidou.lock.spring.boot.autoconfigure.Lock4jProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-08-23 12:18:51.823 INFO 181806 [ main] egate$BeanPostProcessorChecker Bean 'com.baomidou.lock.spring.boot.autoconfigure.LockAutoConfiguration' of type [com.baomidou.lock.spring.boot.autoconfigure.LockAutoConfiguration$$EnhancerBySpringCGLIB$$733da90d] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-08-23 12:18:51.851 INFO 181806 [ main] egate$BeanPostProcessorChecker Bean 'lockKeyBuilder' of type [com.baomidou.lock.DefaultLockKeyBuilder] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-08-23 12:18:51.856 INFO 181806 [ main] egate$BeanPostProcessorChecker Bean 'lockInterceptor' of type [com.baomidou.lock.aop.LockInterceptor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-08-23 12:18:51.860 INFO 181806 [ main] egate$BeanPostProcessorChecker Bean 'lockAnnotationAdvisor' of type [com.baomidou.lock.aop.LockAnnotationAdvisor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

The report only provides Spring startup logs naming Lock4jProperties, LockAutoConfiguration, lockKeyBuilder, lockInterceptor, and lockAnnotationAdvisor; no source files or tests are identified. Start by reproducing the warnings and tracing those named entry points to determine whether distributed-lock proxying is actually affected. Done means the reported behavior is explained and, if it is a bug, covered by a regression test.

Written by the indexing model from the issue text.