Shulou(Shulou.com)06/01 Report--

This article focuses on "how to solve the problems encountered when using EDAS", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve the problems encountered when using EDAS.

I developed and used IntelliJIdea, found the current problem is found in its tomcat log file, so if you have not checked the log file, it is recommended to check it. The log file path is at: C:\ Users\ tom\ .IntelliJIdea 2017.3\ system\ tomcat\ project name\ logs

When using Ali's EDAS, the web project that starts the consumer in development cannot be started, and the console prints the following information:

INFO: spas-client-initializer startJM.Log:INFO Init JM logger with Log4jLoggerFactoryJM.Log:INFO Log root path: C:\ Users\ Vchar\ logs\ JM.Log:INFO Set pandora log path: C:\ Users\ Vchar\ logs\ pandora2018-07-06 18 Users 21 com.taobao.tomcat.container.context.pandora.PandoraManager startInternalINFO: Pandora container started.log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader). Log4j:WARN Please initialize the log4j system properly.log4j:WARN See http: / / logging.apache.org/log4j/1.2/faq.html#noconfig for more info.2018-07-06 18 Error listenerStart2018 21 org.apache.catalina.core.StandardContext startInternalSEVERE: org.apache.catalina.core.StandardContext startInternalSEVERE: Context [] startup failed due to previous errors2018-07-06 18 14 14 com.taobao.tomcat.container.context.pandora.PandoraManager getPandoraLocationINFO: found pandora location from system property: d:\ devtools\ taobao-tomcat-7.0.59 Stopping pandora container: d:\ devtools\ taobao-tomcat-7.0.59\ deploy\ taobao-hsf.sar [EagleEye] [INFO] SelfLog async thread is exited [EagleEye] [INFO] closed AsyncAppender: AsyncAppender [appender=EagleEyeRollingFileAppender [filePath=C:\ Users\ Vchar\ logs\ eagleeye\ eagleeye-self.log] INFO: spas-client-initializer stop2018-07-06 18 com.taobao.tomcat.container.context.pandora.PandoraManager stopInternalINFO 2141853 com.taobao .tomcat.container.context.pandora.PandoraManager stopInternalINFO: Pandora container stopped. [2018-07-06 06Fran 21 Artifact Skyecho-Web-New:war exploded 41879] Pandora.PandoraManager Error during artifact deployment. See server log for details.

Follow the prompts to check the logs\ eagleeye\ eagleeye-self.log log file and find the following error:

[ERROR] failed to add tracing to RxJava.java.lang.NoClassDefFoundError: io/reactivex/functions/Consumerat com.taobao.eagleeye.EagleEye.addRxJavaTracing (EagleEye.java:506) at com.taobao.eagleeye.EagleEye.init (EagleEye.java:585) at com.taobao.eagleeye.EagleEye.init (EagleEye.java:616) at com.taobao.eagleeye.EagleEye. (EagleEye.java:529) at com.taobao.eagleeye.EagleEyePandoraService.init (EagleEyePandoraService.java:37) .... Caused by: com.taobao.pandora.common.exception.PandoraLoaderException: [Module-Loader] eagleeye-core: can not load class {io.reactivex.functions.Consumer} after all phase.

But after reading the error prompt, I looked confused and didn't know how to solve it. I looked up it on the Internet for a long time or to no avail. Finally, we went back to Ali's official documents to consult them one by one. When tomcat failed to start, please check the catalina.log and localhost.log log files of tomcat. After consulting the log documents, we found that there was repeated bean injection of colleagues' service, resulting in startup failure. Finally, the project started normally after the solution.

Therefore, after finding an unknown error, it is best to go to these two log file headers to check. Because Ali's Pandora container will overwrite our log configuration file, and they also have a log configuration of their own. Therefore, the information printed by the console may not be comprehensive.

Solutions to other similar problems online:

Solution 1: if you are using the Eclipse; right-click project > properties > targeted runtimes > uncheck the apache tomcat

Solution 2: due to the local launch of multiple projects, the container encountered an error during temporary file synchronization. The solution: add-Dcom.taobao.pandora.tmp_path=D:\ logs\ pandoralog\ coustomer-log to the startup parameters of tomcat, which is a path defined by yourself.

HSF-0016, failed to start the service, control printing error code HSF-0016; solution:

Check whether there is a conflict on port 12200. Generally, Server Bind failure will cause startup failure. If there are multiple network cards and there is a public network IP machine, use-Dhsf.server.ip to specify the local IP.

At this point, I believe you have a deeper understanding of "how to solve the problems encountered when using EDAS". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.