[INFO] create webapp with contextPath: /maven_web

五月 11, 2019 6:05:26 下午 org.apache.coyote.AbstractProtocol init

信息: Initializing ProtocolHandler ["http-bio-8080"]

五月 11, 2019 6:05:26 下午 org.apache.coyote.AbstractProtocol init

严重: Failed to initialize end point associated with ProtocolHandler ["http-bio-8080"]

java.net.BindException: Address already in use: JVM_Bind <null>:8080

	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:407)

	at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:623)

	at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)

	at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)

	at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

	at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

	at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)

	at org.apache.catalina.startup.Tomcat.start(Tomcat.java:341)

	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1238)

	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:592)

	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)

	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)

	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)

	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)

	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)

	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)

	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)

	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)

	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)

	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)

	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)

	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

	at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)

	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)

	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)

	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)

Caused by: java.net.BindException: Address already in use: JVM_Bind

	at java.net.DualStackPlainSocketImpl.bind0(Native Method)

	at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)

	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)

	at java.net.ServerSocket.bind(ServerSocket.java:375)

	at java.net.ServerSocket.<init>(ServerSocket.java:237)

	at java.net.ServerSocket.<init>(ServerSocket.java:181)

	at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)

	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:394)

	... 36 more

五月 11, 2019 6:05:26 下午 org.apache.catalina.core.StandardService initInternal

严重: Failed to initialize connector [Connector[HTTP/1.1-8080]]

org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8080]]

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)

	at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

	at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)

	at org.apache.catalina.startup.Tomcat.start(Tomcat.java:341)

	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1238)

	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:592)

	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)

	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)

	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)

	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)

	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)

	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)

	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)

	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)

	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)

	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)

	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)

	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

	at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)

	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)

	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)

	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)

Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed

	at org.apache.catalina.connector.Connector.initInternal(Connector.java:983)

	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

	... 31 more

Caused by: java.net.BindException: Address already in use: JVM_Bind <null>:8080

	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:407)

	at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:623)

	at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)

	at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)

	at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)

	... 32 more

Caused by: java.net.BindException: Address already in use: JVM_Bind

	at java.net.DualStackPlainSocketImpl.bind0(Native Method)

	at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)

	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)

	at java.net.ServerSocket.bind(ServerSocket.java:375)

	at java.net.ServerSocket.<init>(ServerSocket.java:237)

	at java.net.ServerSocket.<init>(ServerSocket.java:181)

	at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)

	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:394)

	... 36 more

原因：

之前项目开启的tomcat服务器没关闭，导致8080端口被占用。

解决办法：

查看具体哪个tomcat服务器没关，将其关掉就好了

idea使用maven中的tomcat插件开启服务出现java.net.BindException: Address already in use: JVM_Bind :8080错误原因的更多相关文章

  1. No plugin found for prefix 'tomcat' in the current project and in the plugin groups和java.net.BindException: Address already in use: JVM_Bind <null>:8080的错误解决

    错误报告:No plugin found for prefix 'tomcat' in the current project and in the plugin groups [org.apache ...

  2. （解决tomcat端口被占用的问题）create[8005]java.net.BindException: Address already in use: JVM_Bind

    create[8005]java.net.BindException: Address already in use: JVM_Bind”,原来是Tomcat8005端口被其他进程占用,8005端口是 ...

  3. 【tomcat】启动报错：Failed to initialize end point associated with ProtocolHandler ["http-apr-8080"] java.lang.Exception: Socket bind failed 和java.net.BindException: Address already in use: JVM_Bind错误解决

    背景:[新手] 将开发机子上的Tomcat连同其中的项目,一起拷贝到服务器上,启动tomcat的start.bat,然后报错如下: 问题1: Failed to initialize end poin ...

  4. IDEA中debug启动tomcat报错。Error running t8:Unable to open debugger port(127.0.0.1:49225):java.net.BindException"Address alread in use:JVM_Bind"

    解决办法: 1,如下图打开项目配置的tomcat的“Edit Configurations...” 2,打开“Startup/Connection”--------"Debug"- ...

  5. tomcat运行时候出现java.net.BindException: Address already in use: JVM_Bind错误解决方法

    问题原因:我们在运行tomcat时候一般用8080端口,但是当端口被占用的时候便不能正常使用tomcat并且会造成上述的错误.而端口被占用的原因有很多,这次的原因是因为装好tomcat以后已经启动了一 ...

  6. [已解决]Tomcat启动报 java.net.BindException: Address already in use: JVM_Bind

    启动多个Tomcat的的时候记得要改3个端口: <Server port="8001" shutdown="SHUTDOWN"> <Conne ...

  7. Maven项目-端口被占用java.net.BindException: Address already in use: JVM_Bind <null>:8080解决方法

    异常显示: 问题所在:之前启动的tomcat未停止,端口被占用. 解决方法: 养成良好的习惯,用完之后停掉服务.

  8. eclipse maven项目中使用tomcat插件部署项目

    maven的tomcat插件部署web项目,我简单认为分两种,一种是部署到内置tomcat,另一种是部署到安装的tomcat. 第一种部署,默认是部署在内置tomcat的8080端口,如果不需要改端口 ...

  9. Tomcat启动时报错：java.net.BindException: Permission denied <null>:80 【转载】

    本文转载自: http://blog.sina.com.cn/s/blog_4550f3ca0101g37l.html   问题起因:做负载均衡时需要将Web工程与Wap工程同时部署在一台Suse服务 ...

随机推荐

  1. 全栈项目|小书架|微信小程序-实现搜索功能

    效果图 上图是小程序端实现的搜索功能效果图. 从图中可以看出点击首页搜索按钮即可进入搜索页面. 布局样式是:搜索框 + 热搜内容 + 搜索列表. 搜索框使用 lin-ui 中的 Searchbar组件 ...

  2. #华为云·寻找黑马程序员# 如何实现一个优雅的Python的Json序列化库

    在Python的世界里,将一个对象以json格式进行序列化或反序列化一直是一个问题.Python标准库里面提供了json序列化的工具,我们可以简单的用json.dumps来将一个对象序列化.但是这种序 ...

  3. .Net Core Web Api使用模型验证验证参数合法性

    在接口开发过程中免不了要去验证参数的合法性,模型验证就是帮助我们去验证参数的合法性,我们可以在需要验证的model属性上加上Data Annotations特性后就会自动帮我们在action前去验证输 ...

  4. Redis Cluster 自动化安装，扩容和缩容

    Redis Cluster 自动化安装,扩容和缩容 之前写过一篇基于python的redis集群自动化安装的实现,基于纯命令的集群实现还是相当繁琐的,因此官方提供了redis-trib.rb这个工具虽 ...

  5. 模电&数电知识整理（不定期更新）

    模电总复习之爱课堂题目概念整理 Chapter 1 1) 设室温情况下某二极管的反偏电压绝对值为1V,则当其反偏电压值减少100mV时,反向电流的变化是基本不发生变化. 2) 二极管发生击穿后,在击穿 ...

  6. JS实现链式调用 a().b().c()

    function a() { this.b = function () { console.log('111') return this } this.c = function () { consol ...

  7. 2019 The Preliminary Contest for ICPC China Nanchang National Invitational（A 、H 、I 、K 、M）

    A. PERFECT NUMBER PROBLEM 题目链接:https://nanti.jisuanke.com/t/38220 题意: 输出前五个完美数 分析: 签到.直接百度完美数输出即可 #i ...

  8. UWP GraphQL数据查询的实现

    1. 缘起 Facebook 的移动应用从 2012 年就开始使用 GraphQL.GraphQL 规范于 2015 年开源,现已经在多种环境下可用,并被各种体量的团队所使用. 在这个链接可以看到更多 ...

  9. java之线程（线程的创建方式、java中的Thread类、线程的同步、线程的生命周期、线程之间的通信）

    CPU:10核 主频100MHz 1核  主频    3GHz 那么哪一个CPU比较好呢? CPU核不是越多越好吗?并不一定.主频用于衡量GPU处理速度的快慢,举个例子10头牛运送货物快还是1架飞机运 ...

  10. PDF提取表格的网页工具——Excalibur

      在之前的文章另类爬虫:从PDF文件中爬取表格数据中,我们知道如何利用Python的camelot模块,通过写Python程序来提取PDF中的表格数据.本文我们将学习如何用更便捷的工具从PDF中提取 ...