解決啟動Tomcat報錯:Failed to destroy end point associated with ProtocolHandler["ajp-nio-8009"]
前景提要:我們安裝的maven倉庫預設情況下都放在了C盤中的m2/repository中,但windows使用者的作業系統都安裝在C盤,把maven倉庫放在C盤是很危險的,為此我們需要修改本地倉庫路徑。今天把框架中的maven依賴庫更換了下載地址和存放的位置,因為之前用的都是官網,下載包或者更新配置檔案的速度都特別慢,實在是忍受不了更換更了阿里雲提供的maven倉庫,感覺速度一下子就提升了n個等級,當然這個錯誤也是我在更改之後執行Tomcat之後出現的錯誤。
問題原因:因為自己更改了Maven倉庫的settings.xml的位置,所以配置環境和之前預設的環境變數不一致導致Tomcat執行出錯。
解決方法:
1.開啟myeclipse點選windows->preferences->maven->installations下add一個已經安裝到D:\Java目錄下的maven,如:D:\Java\maven-3.0.4,並勾選此新加項。並點選下面的browse按鈕開啟maven的全域性配置檔案,如:D:\Java\maven-3.0.4\conf\setting.xml。(如已經安裝好可跳過此步)
2.開啟myeclipse點選windows->preferences->maven->User setting下修改user setting選項為:D:\Java\m2\repository\settings.xml,並點選update settings。並點選下面的reindex按鈕更新索引。
3.點選配置視窗的apply按鈕,突出配置視窗。
4.最後開啟CMD,執行mvn help:system會發現Maven從遠端庫下載的jar包都會放到新修改後的路徑D:\Java\m2\repository中了。
相關文章
- 解決Tomcat啟動報錯問題:Failed to destroy end point associated with ProtocolHandler["ajp-nio-8009"]TomcatAIProtocol
- tomcat啟動出現錯誤:Failed to destroy end point associated with ProtocolHandler["ajp-nio-8009"]TomcatAIProtocol
- 嚴重: Failed to destroy end point associated with ProtocolHandler ["ajp-nio-8009"] java.lang.NullPointAIProtocolJavaNull
- org.apache.coyote.AbstractProtocol.destroy Failed to destroy end point associated with ProtocolHandlApacheProtocolAI
- SVN報錯“Failed to run the WC DB work queue associated with”解決辦法AI
- Tomcat啟動報錯:Error starting static Resources解決方法TomcatError
- IDEA啟動時報Failed to create JVM錯誤的解決IdeaAIJVM
- PyCharm啟動報錯:Failed to create JVM.解決辦法之一PyCharmAIJVM
- 解決ProtocolHandler ["ajp-nio-8009"] java.net.BindException: Address already in use: bind問題ProtocolJavaIndexException
- 解決啟動openfeign報錯
- 啟動idea時, 碰到"failed to load jvm DLL ..."錯誤 解決方案IdeaAIJVM
- ElasticSearch啟動報錯 ERROR: [4] bootstrap checks failedElasticsearchErrorbootAI
- clipboard.destroy報錯
- zabbix-server啟動報錯解決Server
- Oracle啟動報錯:ORA-03113: end-of-file on communication channelOracle
- 啟動IDEA 報 failed to load jvm dll XXX 錯誤IdeaAIJVM
- Vue 啟動專案報錯 Failed to compile with 2 errorsVueAICompileError
- keepalived啟動報錯解決一例
- 解決 Rust WebAssembly 啟動 Web 程式報錯RustWeb
- tomcat無法啟動的解決方法Tomcat
- tomcat-啟動報錯Multiple Contexts have a path of "/xxxx"TomcatContext
- ubuntu下git報錯fatal: The remote end hung up unexpectedly解決方案UbuntuGitREM
- idea系列:解決啟動 failed to load JVM DLL 提示IdeaAIJVM
- tomcat啟動報錯java.util.zip.ZipException:invalidCENheader(badsignature)TomcatJavaExceptionHeader
- 解決MMM啟動監控報錯的問題
- Maven工程 服務提供方啟動時沒有Starting ProtocolHandler的 解決方法MavenProtocol
- Tomcat啟動時Initializing Spring FrameworkServlet 'springmvc'卡住,並且不報錯TomcatFrameworkServletSpringMVC
- maven外掛 tomcat7啟動報錯,異常如下MavenTomcat
- 解決docker啟動映象報錯:docker: Error response from daemonDockerError
- 解決Gitlab的The remote end hung up unexpectedly錯誤GitlabREM
- imagick使用readImage報錯 Failed to read the file 或者沒有報錯內容的解決方法AI
- PHP報錯getimagesize(): SSL operation failed with code 1問題解決方案PHPAI
- NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load xxxx錯誤解決方法ErrorAIXMLHTTP
- Docker Desktop啟動報錯:Failed to set version to docker-desktop: exit code: -1DockerAI
- 升級到 MySQL 8.4,MySQL 啟動報錯:io_setup() failed with EAGAINMySqlAI
- 啟動 idea 彈出“Failed to load JVM DLL\bin\server\jvm.dll”錯誤的解決方法IdeaAIJVMServer
- tomcat報錯org.apache.catalina.core.ContainerBase.startInternal A child container failed during startTomcatApacheAI
- Doris建立表報錯Failed to find enough host with storage medium問題解決AI