Cargo
  1. Cargo
  2. CARGO-1102

jboss42x remote deploy failure: pointing to wrong war filename?

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.2.1
    • Fix Version/s: None
    • Component/s: JBoss, Maven2
    • Labels:
      None
    • Environment:
      Mac 10.6.8, Ubuntu 11.10
    • Complexity:
      Intermediate
    • Number of attachments :
      3

      Description

      I only see failure when I'm trying to remote deploy to a JBoss 4.2.3 GA instance. I've ensured the servers can speak to each other, and I've manually placed a war on the deploying server's normal (port 80) webserver and manually crafted the URL the Cargo makes to hit it, and that works fine, too. So all connectivity seems fine.

      The only things that seems to me to be wrong is that the filename in the URL in the example at http://cargo.codehaus.org/JBoss+Remote+Deployer#JBossRemoteDeployer-JBoss40xand42x contains "-1.0-SNAPSHOT" and even though I am trying to deploy a snapshot, too, I only have "fly-garmin.war" with no version or "-SHAPSHOT".

      Here is what I have in my POM...

      <plugin>  
        <groupId>org.codehaus.cargo</groupId>  
        <artifactId>cargo-maven2-plugin</artifactId> 
        <version>1.2.1</version> 
        <configuration>  
          <container>  
            <containerId>jboss42x</containerId>  
            <type>remote</type>  
          </container>
          <configuration>  
            <type>runtime</type>  
            <properties>
              <cargo.remote.username>foo</cargo.remote.username>
              <cargo.remote.password>bar</cargo.remote.password>
              <cargo.hostname>dflyproxy.garmin.com</cargo.hostname>
              <cargo.servlet.port>80</cargo.servlet.port>
              <cargo.jboss.remotedeploy.port>8980</cargo.jboss.remotedeploy.port>
              <cargo.logging>high</cargo.logging>
            </properties> 
          </configuration>  
        </configuration>  
        <executions>
          <execution>
            <id>start-container</id>
            <phase>pre-integration-test</phase>
            <goals>
              <goal>deploy</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
      
      1. logged-failure.txt
        20 kB
        Ken Martin
      2. logged-success.txt
        35 kB
        Ken Martin
      3. new-logged-failure.txt
        38 kB
        Ken Martin

        Activity

        Hide
        Savas Ali Tokmen added a comment -

        Hi Ken

        OK, I would then propose to close this ticket as "Cannot reproduce", and if you want add a note in the JBoss remote deployer's documentation.

        Agree?

        Cheers

        Show
        Savas Ali Tokmen added a comment - Hi Ken OK, I would then propose to close this ticket as "Cannot reproduce", and if you want add a note in the JBoss remote deployer's documentation. Agree? Cheers
        Hide
        Ken Martin added a comment -

        Well, I suppose we could, but that means this really doesn't work for continuous integration, which is what we'd like to be doing with it.

        Is there anything I can do to better log what's happening with SimpleFileServer? If it has errors, where might they be written to?

        Show
        Ken Martin added a comment - Well, I suppose we could, but that means this really doesn't work for continuous integration, which is what we'd like to be doing with it. Is there anything I can do to better log what's happening with SimpleFileServer? If it has errors, where might they be written to?
        Hide
        Savas Ali Tokmen added a comment -

        Hi Ken

        For the ports, you can use the org.codehaus.mojo:build-helper-maven-plugin's reserve-network-port goal; this way it will always reserve some unused ports. Example: http://svn.codehaus.org/cargo/extensions/trunk/maven2/samples/pom.xml

        Else, if you run mvn with the -X option, you will see the log messages listed in: http://svn.codehaus.org/cargo/core/trunk/containers/jboss/src/main/java/org/codehaus/cargo/container/jboss/internal/SimpleHttpFileServer.java

        Cheers

        Show
        Savas Ali Tokmen added a comment - Hi Ken For the ports, you can use the org.codehaus.mojo:build-helper-maven-plugin's reserve-network-port goal; this way it will always reserve some unused ports. Example: http://svn.codehaus.org/cargo/extensions/trunk/maven2/samples/pom.xml Else, if you run mvn with the -X option, you will see the log messages listed in: http://svn.codehaus.org/cargo/core/trunk/containers/jboss/src/main/java/org/codehaus/cargo/container/jboss/internal/SimpleHttpFileServer.java Cheers
        Hide
        Savas Ali Tokmen added a comment -

        Hi Ken

        Any news?

        Cheers

        Show
        Savas Ali Tokmen added a comment - Hi Ken Any news? Cheers
        Hide
        Savas Ali Tokmen added a comment -

        Issue cannot be reproduced when org.codehaus.mojo:build-helper-maven-plugin's reserve-network-port goal is used (i.e., reserved unused ports are always used).

        Example: http://svn.codehaus.org/cargo/extensions/trunk/maven2/samples/pom.xml

        Show
        Savas Ali Tokmen added a comment - Issue cannot be reproduced when org.codehaus.mojo:build-helper-maven-plugin's reserve-network-port goal is used (i.e., reserved unused ports are always used). Example: http://svn.codehaus.org/cargo/extensions/trunk/maven2/samples/pom.xml

          People

          • Assignee:
            Unassigned
            Reporter:
            Ken Martin
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: