What if dubbo can't transfer the dubbo service?

This article mainly explains "what to do if dubbo can not transfer dubbo service". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what to do if dubbo can't get dubbo service".

In the test environment, the cloud service calls the dubbo service and then the dubbo. Other services share a zk with this service, one of which is always not registered. Every time dubbo is called, no data is found and the service fails to start. The trace log is as follows

Java.lang.IllegalStateException: Logback configuration error detected: ERROR in ch.qos.logback.core.joran.util.PropertySetter@7fbe847c-Could not invoke method addDestination in class net.logstash.logback.appender.LogstashTcpSocketAppender with parameter of type java.lang.String java.lang.reflect.InvocationTargetExceptionERROR in net.logstash.logback.appender.LogstashTcpSocketAppender [LOGSTASH]-No destination was configured. Use to add one or more destinations to the appender at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration (LogbackLoggingSystem.java:162) at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithConventions (AbstractLoggingSystem.java:81) at org.springframework.boot.logging.AbstractLoggingSystem.initialize (AbstractLoggingSystem.java:59) at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize (LogbackLoggingSystem.java:115) at org.springframework.boot.logging.LoggingApplicationListener.initializeSystem (LoggingApplicationListener.java:303) at org.springframework.boot Initialize (LoggingApplicationListener.java:276) at org.springframework.boot.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent (LoggingApplicationListener.java:239) at org.springframework.boot.logging.LoggingApplicationListener.onApplicationEvent (LoggingApplicationListener.java:212) at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener (SimpleApplicationEventMulticaster.java:167) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent (SimpleApplicationEventMulticaster.java:139) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent (SimpleApplicationEventMulticaster.java:122) at org.springframework.boot .context.event.EventPublishingRunListener.environmentPrepared (EventPublishingRunListener.java:73) at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared (SpringApplicationRunListeners.java:54) at org.springframework.boot.SpringApplication.prepareEnvironment (SpringApplication.java:336) at org.springframework.boot.SpringApplication.run (SpringApplication.java:307) at org.springframework.boot.builder.SpringApplicationBuilder.run (SpringApplicationBuilder.java:134) at cn.com.esgcc.PlaneServiceApplication.main (PlaneServiceApplication.java:22) at sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethod) At sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.springframework.boot.loader.MainMethodRunner.run (MainMethodRunner.java:48) at org.springframework.boot.loader.Launcher.launch (Launcher.java:87) at org.springframework.boot.loader.Launcher.launch (Launcher.java:50) at org.springframework.boot.loader. JarLauncher.main (JarLauncher.java:51) Could not invoke method addDestination in class net.logstash.logback.appender.LogstashTcpSocketAppender with parameter of type java.lang.String java.lang.reflect.InvocationTargetException

The other information of the log is the associated service jar package, probably because the acquisition parameter cannot be found.

Switch branch lookup. After corresponding to zk,redis address, logstash port number is the same as push package jps-lxxxxxxxxxx .jarvim xxxxxxxxxx .jar: / xx.properties return zk address is correct, redis address correctly restarts java-jar xxxxxx.jar-- spring.profiles.active=dev troubleshooting is unexpectedly due to a callback address not added, resulting in @ Value () to get the configuration file. Thank you for reading. This is the content of "what to do if dubbo cannot call dubbo service". After the study of this article, I believe that we have a deeper understanding of what to do when dubbo can not transfer the dubbo service, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!