mysql - Maven - Tomcat 7 - Hibernate MySQL : Broken Pipe Exception when doing mvn deploy

标签 mysql hibernate maven spring-mvc tomcat

对于我学校的编程考试,我们需要能够在 Tomcat (7) 服务器上使用 maven 构建和部署 Spring MVC 项目。这些东西大部分都在工作。 mvn clean install 提供了 BUILD SUCCESS,这很好,我可以设置我的 tomcat 服务器。但是,当我尝试使用例如 mvn tomcat7:deploy 来运行或部署我的项目时,我收到了损坏的管道异常,它看起来像这样:

[ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project SpringMVCBlog: Cannot invoke Tomcat manager: Broken pipe -> [Help 1]

完整的堆栈跟踪 (mvn tomcat7:deploy -e) 如下:

[ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project SpringMVCBlog: Cannot invoke Tomcat manager: Protocol wrong type for socket -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project SpringMVCBlog: Cannot invoke Tomcat manager
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
    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:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
    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:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke Tomcat manager
    at org.apache.tomcat.maven.plugin.tomcat7.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:141)
    at org.apache.tomcat.maven.plugin.tomcat7.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:68)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    ... 19 more
Caused by: java.net.SocketException: Protocol wrong type for socket
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:181)
    at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:115)
    at org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:880)
    at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:89)
    at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108)
    at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:117)
    at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:265)
    at org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:203)
    at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:236)
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:121)
    at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:486)
    at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
    at org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:742)
    at org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:705)
    at org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:388)
    at org.apache.tomcat.maven.plugin.tomcat7.deploy.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:85)
    at org.apache.tomcat.maven.plugin.tomcat7.deploy.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:82)
    at org.apache.tomcat.maven.plugin.tomcat7.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:132)
    ... 22 more

我已经为此苦苦挣扎了很长时间,但似乎一直找不到解决方案。当我使用 glassfish 服务器在 IDE (IntelliJ) 中运行此项目时,它可以工作,但目标是使用终端(我在 Mac 上)运行它并将其部署在 Tomcat 服务器上。

我已经搜索过,但没有太多关于破损管道异常的信息。我发现它与Hibernate和MySQL有关。我在应用程序中有一个基本的 Hibernate 结构,只有一个基本的 hibernate.cfg/xml 和一些设置,以及一个用于获取 session 的 Util 类,以便我可以在数据库上保存和更新。损坏的管道与连接池有关,据我所知,我在项目中没有使用连接池。

我真的希望有人能帮助我,这个问题非常令人沮丧。请告诉我是否需要任何额外的代码!

编辑

我的 pom.xml 的构建部分的内容:

<build>
      <plugins>
          <plugin>
              <groupId>org.apache.tomcat.maven</groupId>
              <artifactId>tomcat7-maven-plugin</artifactId>
              <version>2.2</version>
          </plugin>
      </plugins>
      <pluginManagement>
          <plugins>
              <plugin>
                  <groupId>org.apache.tomcat.maven</groupId>
                  <artifactId>tomcat7-maven-plugin</artifactId>
                  <version>2.2</version>
                  <configuration>
                      <url>http://localhost:8080/manager/text</url>
                      <server>TomcatServer</server>
                      <username>root</username>
                      <password>root</password>
                      <path>/SpringMVCBlog</path>
                      <update>true</update>
                  </configuration>
              </plugin>
          </plugins>
      </pluginManagement>
    <finalName>SpringMVCBlog</finalName>
  </build>

最佳答案

只需使用

mvn tomcat7:redeploy

如果您的应用程序已部署。

否则,您需要先取消部署应用程序,然后再执行mvn tomcat7:deploy

关于mysql - Maven - Tomcat 7 - Hibernate MySQL : Broken Pipe Exception when doing mvn deploy,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/27669143/

相关文章:

PHP/MySQL 安全问题

java - 如何处理@AttributeOverrides上的@Type

java - Maven 3.8.0 编译器 - 编译时出现 fatal error : release version 11 not supported

spring - 如何避免将特定版本的 Spring Boot 放入库中

java - maven 是否能够在没有任何源的情况下将单个 *.dll 打包到 jar 中?

php - php中的手机型号检测

mysql - BIRT 中的 Select 语句提供与 MySQL Workbench 不同(且错误)的输出

mysql - 检查给定日期存在于 MySQL 中的 2 个日期字段之间

java - 保存从Entity扩展的实例

java - 从数据库中检索特定数量的记录 - JPA(提高性能)