proxy settings are still used during deployment

Vlad Skarzhevskyy added a comment - 28/Sep/11 1:37 AM server pom

Vlad Skarzhevskyy added a comment - 28/Sep/11 1:38 AM strip down settings

Savas Ali Tokmen added a comment - 28/Sep/11 1:19 PM That's weird, CARGO normally does not use proxy settings when deploying. Can you please mvn with the -X option and attach the output as a log file?

Vlad Skarzhevskyy added a comment - 28/Sep/11 2:03 PM I think the problem is triggered when maven actually needs to go via proxy and retrieve something there. Today I run it couple of times mvn -P deploy -U deploy (and it failed) mvn -P deploy -X -U deploy > single-module_ok.log (and it did not failed) mvn -P deploy -X -U -up deploy > single-module_up1-err.log (failed) mvn -P deploy -X -U -up deploy > single-module_up2-err.log (failed) mvn -P deploy -X -U deploy > single-module_u2-err.log (failed) mvn -P deploy -X -U deploy > single-module_u3-err.log (failed) mvn -P deploy -X deploy > single-module_r-last.log (OK) will attach all logs in minute.

Savas Ali Tokmen added a comment - 28/Sep/11 3:20 PM Interesting... Does it also fail when you for example do any of the commands twice? I see in the logs: Caused by: org.codehaus.cargo.container.ContainerException: Failed to undeploy [D:\build\work\mco2\mco2-runner\mco2-server\target\mco2.war] at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.undeploy(AbstractTomcatManagerDeployer.java:142) at org.codehaus.cargo.maven2.DeployerUndeployMojo.performDeployerActionOnSingleDeployable(DeployerUndeployMojo.java:40) at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:152) at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:64) at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:279) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) ... 20 more Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://torvspocapp:9040/manager/text/list at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:507) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:644) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:657) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.undeploy(AbstractTomcatManagerDeployer.java:125) ... 25 more ... and this looks more like the Tomcat server failing. Did you also have a chance to check with Wireshark to see what server it is actually connecting to?

Vlad Skarzhevskyy added a comment - 28/Sep/11 3:27 PM I see on proxy server that we are connecting via proxy and not directly! The proxy is giving the 503. When I use "-U -up" it is failing. For now I removed -U from my configuration on crusiecontrol. Will see it it helps today at 1 AM.

Savas Ali Tokmen added a comment - 08/Apr/12 3:57 AM Hi Vlad Any news? Thank you

Vlad Skarzhevskyy added a comment - 08/Apr/12 2:07 PM - edited Now I use cargo-maven2-plugin 1.2.0. Still the same problem. When I run build first time during the day it will fail during deploy. I think this because because maven does SNAPSHOT dependency update using proxy. All next builds at the same day will run fine. Next day the same problem.

Savas Ali Tokmen added a comment - 08/Apr/12 4:07 PM Hi Vlad Can you please try version 1.2.2-SNAPSHOT? Instructions are on http://cargo.codehaus.org/Maven2+Plugin+Installation#snapshots Thank you

Vlad Skarzhevskyy added a comment - 08/Apr/12 8:46 PM I was unable to find the documentation for configuration changes for 1.2.2-SNAPSHOT When I try to run with previous configuration: Got the error: [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.2-SNAPSHOT:deployer-undeploy (clean-undeploy) on project entree-server: Execution clean-undeploy of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.2-SNAPSHOT:deployer-undeploy failed: Cannot create configuration. There's no registered configuration for the parameters (container [id = [tomcat6x] , type = [remote] ], configuration type [runtime] ). Actually there are no valid types registered for this configuration. Maybe you've made a mistake spelling it? -> [Help 1] My configuration: ---- <profile> <id>deploy</id> <build> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.2.2-SNAPSHOT</version> <executions> <execution> <id>verify-deploy</id> <phase>install</phase> <goals> <goal>deployer-deploy</goal> </goals> </execution> <execution> <id>clean-undeploy</id> <phase> package </phase> <goals> <goal>deployer-undeploy</goal> </goals> </execution> </executions> <configuration> <container> <containerId>tomcat7x</containerId> <type>remote</type> </container> <configuration> <type>runtime</type> <properties> <cargo.remote.uri>${tomcat-url}/manager/text</cargo.remote.uri> <cargo.remote.username>${tomcat-username}</cargo.remote.username> <cargo.remote.password>${tomcat-pwd}</cargo.remote.password> </properties> </configuration> <deployer> <type>remote</type> <deployables> <deployable> <groupId>${project.groupId}</groupId> <artifactId>${project.artifactId}</artifactId> <type>war</type> <pingURL>${tomcat-url}/${deployableName}/index.html</pingURL> <pingTimeout>180000</pingTimeout> <properties> <context>${deployableName}</context> </properties> </deployable> </deployables> </deployer> </configuration> </plugin> </plugins> </build> </profile>

Savas Ali Tokmen added a comment - 09/Apr/12 2:51 AM Hi Vlad For the documentation, you can search for cargo dev r3286: http://comments.gmane.org/gmane.comp.java.cargo.devel/12637 Can you please attach your full pom.xml? The extract mentions tomcat7x, whereas the error message is for tomcat6x -I therefore suspect you have another profile set elsewhere. Thank you

Vlad Skarzhevskyy added a comment - 09/Apr/12 2:54 AM I have two projects one with tomcat 6 and other with tomcat 7 - non working

Vlad Skarzhevskyy added a comment - 09/Apr/12 2:57 AM this the example pom with real company name replaced, just in case

Savas Ali Tokmen added a comment - 09/Apr/12 3:19 AM Hi Vlad Please follow the insturctions on http://cargo.codehaus.org/Maven2+Plugin+Installation#snapshots completely: you need to declare both the pluginRepository and repository, due to the way how the CARGO plugin's container artifact loading mechanism works. Thank you

Vlad Skarzhevskyy added a comment - 09/Apr/12 1:12 PM Sorry. My mistake. Now I change the builds to use 1.2.2-SNAPSHOT. The build is passing today. Will let you know if this resolved the problem with proxy.

Savas Ali Tokmen added a comment - 12/Apr/12 1:31 PM Hi Vlad Any news? Cheers

Vlad Skarzhevskyy added a comment - 12/Apr/12 2:13 PM All good for last two days with 1.2.2-SNAPSHOT. The problem that I had before did not appeared.

Savas Ali Tokmen added a comment - 12/Apr/12 2:27 PM Perfect, closing the issue, then