zhengcling opened a new issue, #7944:
URL: https://github.com/apache/incubator-seata/issues/7944

   ### Check Ahead
   
   - [x] I have searched the [issues](https://github.com/seata/seata/issues) of 
this repository and believe that this is not a duplicate.
   
   - [ ] I am willing to try to fix this bug myself.
   
   
   ### Ⅰ. Issue Description
   
   Windows Seata2.4.0 + Nacos客户端启动报错
   
   ### Ⅱ. Describe what happened
   
   org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'globalTransactionScanner' defined in class path resource 
[org/apache/seata/spring/boot/autoconfigure/SeataAutoConfiguration.class]: null
   Caused by: java.lang.ExceptionInInitializerError: 
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:421)
        at java.base/java.lang.Class.forName(Class.java:412)
        at 
org.apache.seata.spring.annotation.GlobalTransactionScanner.findBusinessBeanNamesNeededEnhancement(GlobalTransactionScanner.java:523)
        at 
org.apache.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:501)
        at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1873)
        at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1822)
   
   
   ### Ⅲ. Describe what you expected to happen
   
   启动成功
   
   
   ### Ⅳ. How to reproduce it (as minimally and precisely as possible)
   
   JDK21
   
   Client pom.xml
   ```
   <dependency>
       <groupId>com.alibaba.cloud</groupId>
       <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
       <version>2023.0.3.2</version>
   </dependency>
   <dependency>
       <groupId>com.alibaba.cloud</groupId>
       <artifactId>spring-cloud-starter-alibaba-seata</artifactId>
       <version>2023.0.3.2</version>
       <exclusions>
           <exclusion>
               <groupId>org.apache.seata</groupId>
               <artifactId>seata-spring-boot-starter</artifactId>
           </exclusion>
       </exclusions>
   </dependency>
   <dependency>
       <groupId>org.apache.seata</groupId>
       <artifactId>seata-spring-boot-starter</artifactId>
       <version>2.4.0</version>
    </dependency>
   ```
   
   application.yml
   
   meta:
     seata:
       nacos:
         server-addr: 127.0.0.1:8848
         namespace: ***
         group: SEATA_GROUP
   seata:
     enabled: true
     application-id: ${spring.application.name}
     # 事务分组, 后面细讲
     tx-service-group: default_tx_group
     enable-auto-data-source-proxy: false
     service:
       vgroup-mapping:
         default_tx_group: default
     registry:
       type: nacos
       nacos:
         # 应与seata-server实际注册的服务名一致
         application: seata-server
         server-addr: ${meta.seata.nacos.server-addr}
         namespace: ${meta.seata.nacos.namespace}
         group: ${meta.seata.nacos.group}
         client-application: ${spring.application.name}
         username: 'nacos'
         password: 'nacos'
         context-path: '/nacos'
     config:
       type: nacos
       nacos:
         server-addr: ${meta.seata.nacos.server-addr}
         namespace: ${meta.seata.nacos.namespace}
         group: ${meta.seata.nacos.group}
         data-id: seataServer.properties
         username: 'nacos'
         password: 'nacos'
         context-path: '/nacos'
     tcc:
       fence:
         log-table-name: tcc_fence_log
         clean-period: 1h
       # You can choose from the following options: fastjson, jackson, gson
       context-json-parser-type: fastjson
   
   ### Ⅴ. Anything else we need to know?
   
   _No response_
   
   ### Ⅵ. Environment
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to