incubator-seata icon indicating copy to clipboard operation
incubator-seata copied to clipboard

:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution.

Results 439 incubator-seata issues
Sort by recently updated
recently updated
newest added

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description https://github.com/apache/incubator-seata/actions/runs/10141899986/job/28040045544 ``` Error: Failed to execute goal...

…ception (#6679) - [X] I have registered the PR [changes](../changes). ### Ⅰ. Describe what this PR did ### Ⅱ. Does this pull request fix one issue? fixes #6679 ### Ⅲ....

## Why you need it? seata-all 下的druid.jar 存在安全漏洞,我应该怎么去解决这个安全漏洞,我们安全机制有点严格 我试过痛过maven打包的时候排除bruid.jar 还是会存在,怎么单独让他升级 ![image](https://github.com/user-attachments/assets/c9accdf1-20c1-4147-94e7-f40f64ebea7d) ## How it could be? A clear and concise description of what you want to happen. You can explain...

## Why you need it? Is your feature request related to a problem? Please describe in details - Provide built-in GraalVM Reachability Metadata on Seata Client 2.1.0+. The GraalVM Reachability...

有什么办法可以在不加全局事务注解的前提下,就可以判断我当前要操作的数据是否被其他全局事务所持有

![image](https://github.com/user-attachments/assets/c968893b-efc1-432e-9dfb-cc4cf0d3b93f) 251行的异常,我们能否判断channelAddress是否为空,如果不为空,说明tc集群只有部分出现了问题无法注册,实际上TC集群是可以提供服务的 这个时候,可能集群是可用的,TM/RM这样直接抛出异常,感觉违背了tc的高可用

When only use shardingsphere : sharding is OK (only choise one db and one table) When only use shardingsphere with seata : sharding is ERROR(Scan all db and table) like...

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description TransactionPropagationInterceptor拦截器在请求异常时无清除线程里的xid,而HTTP请求是通过线程池共享线程的。当下一次请求拿到未清除xid的线程时就会报错。 ### Ⅱ. Describe what happened If...

### Ⅰ. Issue Description AT模式,在同一个分支事务里面,更新两条不同的记录,如果主键包含特殊字符 ; ,会报【branch register failed for key 'lock_table.PRIMARY'】 ### Ⅱ. Describe what happened 客户端往seata-server注册分支事务时,会触发seata-server的【io.seata.server.coordinator.DefaultCoordinator#doBranchRegister】方法,该方法会往【lock_table】插入记录(每锁定一行就插入一条),但是在为每一行锁记录生成该表的 row_key时(详见io.seata.server.lock.AbstractLockManager#collectRowLocks(java.lang.String, java.lang.String, java.lang.String, java.lang.Long, java.lang.Long)),由于有特殊字符【;】,导致主键生成错误,造成锁冲突 业务系统服务错误栈如下: ``` org.springframework.jdbc.UncategorizedSQLException: ### Error updating database....

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description 使用外部扩展,SPI无法加载对应的class,抛出java.lang.ClassNotFoundException:io.seata.sqlparser.druid.dm.DmOperateRecognizerHolder io.seata.common.loader.EnhancedServiceLoader.InnerEnhancedServiceLoader#loadFile 能够扫描到对应的META-INF/services下的自定义文件,如果将新增的扩展类放到seata-all-1.6.1.jar中可以正常使用,如果使用外部扩展则不能使用。使用到的类加载器是io.seata.sqlparser.druid.DruidIsolationClassLoader ### Ⅱ. Describe what...