You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Bug] [Module Name] when springboot integrate with seata, Exception is occured Caused by: io.seata.common.exception.NotSupportYetException: not support registry type: zookeeper
#15926
Open
3 tasks done
binbin0915 opened this issue
Apr 27, 2024
· 2 comments
I had searched in the issues and found no similar issues.
What happened
when springboot integrate with seata, Exception is occured Caused by: io.seata.common.exception.NotSupportYetException: not support registry type: zookeeper
Caused by: java.lang.ExceptionInInitializerError
at io.seata.discovery.registry.RegistryFactory.getInstance(RegistryFactory.java:38) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:256) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.reconnect(NettyClientChannelManager.java:171) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:198) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:220) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:512) ~[seata-all-1.6.1.jar!/:1.6.1]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.31.jar!/:5.3.31]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.31.jar!/:5.3.31]
... 23 more
Caused by: io.seata.common.exception.NotSupportYetException: not support registry type: zookeeper
at io.seata.discovery.registry.RegistryFactory.buildRegistryService(RegistryFactory.java:49) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.discovery.registry.RegistryFactory.access$100(RegistryFactory.java:30) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.discovery.registry.RegistryFactory$RegistryFactoryHolder.(RegistryFactory.java:56) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.discovery.registry.RegistryFactory.getInstance(RegistryFactory.java:38) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:256) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.reconnect(NettyClientChannelManager.java:171) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:198) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:220) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:512) ~[seata-all-1.6.1.jar!/:1.6.1]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.31.jar!/:5.3.31]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.31.jar!/:5.3.31]
... 23 more
it is probably something mixed with dolphin's zookeeper's ip env variables , seata and dolphin 's zookeeper is different. how can i solve this problem
What you expected to happen
seata and dolphin 's zookeeper is different. how can i solve this problem
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
Search before asking
What happened
when springboot integrate with seata, Exception is occured Caused by: io.seata.common.exception.NotSupportYetException: not support registry type: zookeeper
Caused by: java.lang.ExceptionInInitializerError
at io.seata.discovery.registry.RegistryFactory.getInstance(RegistryFactory.java:38) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:256) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.reconnect(NettyClientChannelManager.java:171) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:198) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:220) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:512) ~[seata-all-1.6.1.jar!/:1.6.1]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.31.jar!/:5.3.31]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.31.jar!/:5.3.31]
... 23 more
Caused by: io.seata.common.exception.NotSupportYetException: not support registry type: zookeeper
at io.seata.discovery.registry.RegistryFactory.buildRegistryService(RegistryFactory.java:49) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.discovery.registry.RegistryFactory.access$100(RegistryFactory.java:30) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.discovery.registry.RegistryFactory$RegistryFactoryHolder.(RegistryFactory.java:56) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.discovery.registry.RegistryFactory.getInstance(RegistryFactory.java:38) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:256) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.NettyClientChannelManager.reconnect(NettyClientChannelManager.java:171) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:198) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:220) ~[seata-all-1.6.1.jar!/:1.6.1]
at io.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:512) ~[seata-all-1.6.1.jar!/:1.6.1]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.31.jar!/:5.3.31]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.31.jar!/:5.3.31]
... 23 more
it is probably something mixed with dolphin's zookeeper's ip env variables , seata and dolphin 's zookeeper is different. how can i solve this problem
What you expected to happen
seata and dolphin 's zookeeper is different. how can i solve this problem
How to reproduce
springboot with seata
Anything else
No response
Version
3.2.x
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: