[io.seata.spring.boot.autoconfigure.SeataCoreAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

0h4hbjxa  于 4个月前  发布在  Spring
关注(0)|答案(1)|浏览(67)

Ⅰ. Issue Description

log print "[io.seata.spring.boot.autoconfigure.SeataCoreAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors"

Ⅱ. Describe what happened

starting 2023-03-14 21:01:33.605 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'io.seata.spring.boot.autoconfigure.SeataCoreAutoConfiguration' of type [io.seata.spring.boot.autoconfigure.SeataCoreAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:33.607 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'springApplicationContextProvider' of type [io.seata.spring.boot.autoconfigure.provider.SpringApplicationContextProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:33.610 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'io.seata.spring.boot.autoconfigure.SeataAutoConfiguration' of type [io.seata.spring.boot.autoconfigure.SeataAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:33.805 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'failureHandler' of type [io.seata.tm.api.DefaultFailureHandlerImpl] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:33.886 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'springCloudAlibabaConfiguration' of type [io.seata.spring.boot.autoconfigure.properties.SpringCloudAlibabaConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:33.905 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'seataProperties' of type [io.seata.spring.boot.autoconfigure.properties.SeataProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:33.920 INFO main [traceId= ] [SpanId= ] i.s.s.b.a.SeataAutoConfiguration Automatically configure Seata
starting 2023-03-14 21:01:34.268 INFO main [traceId= ] [SpanId= ] i.s.c.ConfigurationFactory load Configuration from :Spring Configuration
starting 2023-03-14 21:01:34.896 INFO main [traceId= ] [SpanId= ] i.s.s.a.GlobalTransactionScanner Initializing Global Transaction Clients ... 
starting 2023-03-14 21:01:35.472 INFO main [traceId= ] [SpanId= ] i.s.c.r.n.NettyClientBootstrap NettyClientBootstrap has started
starting 2023-03-14 21:01:35.573 INFO main [traceId= ] [SpanId= ] i.s.c.r.n.NettyClientChannelManager will connect to 192.168.12.65:30091
starting 2023-03-14 21:01:35.591 INFO main [traceId= ] [SpanId= ] i.s.c.r.n.NettyPoolableFactory NettyPool create channel to transactionRole:TMROLE,address:192.168.12.65:30091,msg:< RegisterTMRequest{applicationId='onepiece-picture', transactionServiceGroup='default_tx_group'} >
starting 2023-03-14 21:01:36.824 INFO main [traceId= ] [SpanId= ] i.s.c.r.n.TmNettyRemotingClient register TM success. client version:1.5.2, server version:1.5.0-SNAPSHOT,channel:[id: 0xdbf44d6b, L:/10.8.0.232:50197 - R:/192.168.12.65:30091]
starting 2023-03-14 21:01:36.849 INFO main [traceId= ] [SpanId= ] i.s.c.r.n.NettyPoolableFactory register success, cost 853 ms, version:1.5.0-SNAPSHOT,role:TMROLE,channel:[id: 0xdbf44d6b, L:/10.8.0.232:50197 - R:/192.168.12.65:30091]
starting 2023-03-14 21:01:36.855 INFO main [traceId= ] [SpanId= ] i.s.s.a.GlobalTransactionScanner Transaction Manager Client is initialized. applicationId[onepiece-picture] txServiceGroup[default_tx_group]
starting 2023-03-14 21:01:36.903 INFO main [traceId= ] [SpanId= ] i.s.rm.datasource.AsyncWorker Async Commit Buffer Limit: 10000
starting 2023-03-14 21:01:36.916 INFO main [traceId= ] [SpanId= ] i.s.r.d.xa.ResourceManagerXA ResourceManagerXA init ...
starting 2023-03-14 21:01:36.953 INFO main [traceId= ] [SpanId= ] i.s.c.r.n.NettyClientBootstrap NettyClientBootstrap has started
starting 2023-03-14 21:01:36.959 INFO main [traceId= ] [SpanId= ] i.s.s.a.GlobalTransactionScanner Resource Manager is initialized. applicationId[onepiece-picture] txServiceGroup[default_tx_group]
starting 2023-03-14 21:01:36.960 INFO main [traceId= ] [SpanId= ] i.s.s.a.GlobalTransactionScanner Global Transaction Clients are initialized. 
starting 2023-03-14 21:01:36.989 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'io.seata.spring.boot.autoconfigure.SeataDataSourceAutoConfiguration' of type [io.seata.spring.boot.autoconfigure.SeataDataSourceAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:39.374 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'com.alibaba.cloud.seata.feign.SeataFeignClientAutoConfiguration$FeignBeanPostProcessorConfiguration' of type [com.alibaba.cloud.seata.feign.SeataFeignClientAutoConfiguration$FeignBeanPostProcessorConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:39.488 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'seataFeignObjectWrapper' of type [com.alibaba.cloud.seata.feign.SeataFeignObjectWrapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
starting 2023-03-14 21:01:39.864 INFO main [traceId= ] [SpanId= ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'org.springframework.cloud.sleuth.instrument.messaging.TraceMessagingAutoConfiguration$SleuthKafkaConfiguration' of type [org.springframework.cloud.sleuth.instrument.messaging.TraceMessagingAutoConfiguration$SleuthKafkaConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. Start error reporting

Ⅵ. Environment:

  • JDK version : 1.8
  • Seata version:
<dependency>
            <groupId>com.alibaba.cloud</groupId>
            <artifactId>spring-cloud-starter-alibaba-seata</artifactId>
            <version>2.2.2.RELEASE</version>
            <exclusions>
                <exclusion>
                    <groupId>io.seata</groupId>
                    <artifactId>seata-spring-boot-starter</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

        <dependency>
            <groupId>io.seata</groupId>
            <artifactId>seata-spring-boot-starter</artifactId>
            <version>1.5.2</version>
        </dependency>
  • spring boot:2.2.5.RELEASE
rqenqsqc

rqenqsqc1#

This is expected.
Beacuse GlobalTransactionScanner implements Spring BeanPostProcessor ,will be initialized first . this bean dep on springApplicationContextProvider declared in configclass SeataCoreAutoConfiguration .

Of course, this info information can also be optimized.

相关问题