Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-57811

Jenkins trying to create duplicate instance of Tomcat

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • deploy-plugin
    • None

      When you set "clean install" on your root pom. Then Jenkins will try to start a seperate instance of tomcat on your server on the same port. 

      The Jenkins error doesn' t give the right info:
      Caused by: java.net.SocketException: Connection reset

      That's not the real issue. On the server it gives:
      java.net.BindException: Address already in use (Bind failed)

      Jenkins shouldnt be trying to start another instance. Nowhere did I tell Jenkins to be creating other instances. I'm only deploying to 1 tomcat server. 

      This is a blocking defect. Can't use Jenkins with Tomcat anymore.

        1. pom.xml
          2 kB
        2. Screenshot from 2019-06-02 03-50-14.png
          Screenshot from 2019-06-02 03-50-14.png
          428 kB
        3. Screenshot from 2019-06-02 03-51-02.png
          Screenshot from 2019-06-02 03-51-02.png
          13 kB
        4. Screenshot from 2019-06-02 03-51-09.png
          Screenshot from 2019-06-02 03-51-09.png
          32 kB

          [JENKINS-57811] Jenkins trying to create duplicate instance of Tomcat

          Philip Rego added a comment -

          Fails without any goals or options also
          Deploying /var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war to container Tomcat 8.x Remote with context
          [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] is not deployed. Doing a fresh deployment.
          Deploying [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war]
          ERROR: Build step failed with exception
          org.codehaus.cargo.container.ContainerException: Failed to deploy [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war]
          at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:110)
          at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:184)

          Philip Rego added a comment - Fails without any goals or options also Deploying /var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war to container Tomcat 8.x Remote with context [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] is not deployed. Doing a fresh deployment. Deploying [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] ERROR: Build step failed with exception org.codehaus.cargo.container.ContainerException: Failed to deploy [/var/lib/jenkins/workspace/WhatThePhil/target/ROOT.war] at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:110) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:184)

          Robin Jansohn added a comment -

          I have no clue what you are actually trying to do but the deploy-plugin does not start any Tomcat instances. As the name indicates it only deploys WAR/EAR files.

          My guess would be that your Maven configuration (pom.xml) contains something which starts a new Tomcat instance.

          Robin Jansohn added a comment - I have no clue what you are actually trying to do but the deploy-plugin does not start any Tomcat instances. As the name indicates it only deploys WAR/EAR files. My guess would be that your Maven configuration (pom.xml) contains something which starts a new Tomcat instance.

          Robin Jansohn added a comment -

          Closing due to inactivity.

          Robin Jansohn added a comment - Closing due to inactivity.

            Unassigned Unassigned
            philrego Philip Rego
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: