eclipse+maven+tomcat 如何配置调试

0 0

eclipse+maven+tomcat 如何配置调试5

环境:
eclipse Kepler+ maven 3.1 + tomcat7 + tomcat7-maven-plugin
配置教程:
http://wenku.baidu.com/link?url=5Vodlbq97x1LELtEH5CwmX9Rkk_Q3l_jkKF4h3Jx5VwKkPa6cmdR5PL0TK-sktiNQg_tPHiD98bbApCxsJeiLY-vr5ifPSpcM2EWYZA7f0_
问题:
当我按教程配置完后第一次运行成功,第二次运行会报如下错误:
[INFO] >>> tomcat7-maven-plugin:2.1:run (default-cli) @ anuostruts >>>
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ anuostruts ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ anuostruts ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] <<< tomcat7-maven-plugin:2.1:run (default-cli) @ anuostruts <<<
[INFO]
[INFO] --- tomcat7-maven-plugin:2.1:run (default-cli) @ anuostruts ---
[INFO] Running war on http://localhost:8099/anuostruts
[INFO] Using existing Tomcat server configuration at E:\Project\EclipseProject\anuostruts\target\tomcat
[INFO] create webapp with contextPath: /anuostruts
十二月 30, 2013 11:29:10 上午 org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8099"]
十二月 30, 2013 11:29:10 上午 org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-8099"]
java.net.BindException: Address already in use: JVM_Bind <null>:8099
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:406)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
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:335)
at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1091)
at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:512)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:46)
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:96)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:175)
at java.net.ServerSocket.bind(ServerSocket.java:376)
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:393)
... 35 more

好久都没解决到:求大神帮助,感激不尽.

或者推荐些其他调试方法,感觉在eclipse下调试maven项目很麻烦!!!

2013年12月30日 11:40

Anuo.
15
0 0 3

4个答案按时间排序按投票排序

0 0

感觉是第一次启动的tomcat服务没关闭，又启了一个tomcat服务，第二次启动的时候报端口被占用的错误。

2014年1月02日 15:58

q894523017
30
0 0 0

添加评论

0 0

Kill the proces occupying the port 8099 from command Windows. YOU ca-n Find the proces id from task manager.

2014年1月02日 00:37

xzcgeorge
32
0 0 1

添加评论

0 0

1、首先确定工程已经转变为maven工程结构；
2、在web工程上右键属性，找到project Facets，确定选中了dynamic webModule、java、javascript三个选项
3、有了第二步，才能在web工程上右键属性找到deployment assembly选项，确定里边有/src/main/java、/src/main/resources、/src/main/webapp、其他maven module（如果依赖其他maven module的话）、maven Dependencies（如果没有可以通过add添加）
4、window-》show views-》输入servers，打开servers，然后右键new-》server，按照步骤操作即可，最终启动tomcat，即可本地进行热部署调试等。

2014年1月01日 00:13

ycfdonews
31
0 0 0

添加评论

0 0

java.net.BindException: Address already in use: JVM_Bind <null>:8099
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:406)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)

2013年12月30日 13:26