We're updating the issue view to help you get more done. 

The deployer pingTimeout logs are not displayed anywhere

Description

We configure the pingTimeout to 10000 and containerTimeout to 180000 but the pingTimeout is not respected

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 build 02-Jan-2013 14:58:50 [DEBUG] Configuring mojo 'org.codehaus.cargo:cargo-maven2-plugin:1.3.1:start' with basic configurator --> build 02-Jan-2013 14:58:50 [DEBUG] (f) type = existing build 02-Jan-2013 14:58:50 [DEBUG] (s) home = /opt/apps/Test build 02-Jan-2013 14:58:50 [DEBUG] (s) properties = {cargo.jetty.createContextXml=false, cargo.jvmargs=-Xms4m -Xmx16m, cargo.process.spawn=true, cargo.runtime.args=--ini=/opt/apps/Test/etc/start.ini, cargo.servlet.port=10000} build 02-Jan-2013 14:58:50 [DEBUG] (f) configuration = org.codehaus.cargo.maven2.configuration.Configuration@4214795e build 02-Jan-2013 14:58:50 [DEBUG] (s) containerId = jetty7x build 02-Jan-2013 14:58:50 [DEBUG] (f) type = installed build 02-Jan-2013 14:58:50 [DEBUG] (s) home = /opt/apps/Test/jetty build 02-Jan-2013 14:58:50 [DEBUG] (s) timeout = 180000 build 02-Jan-2013 14:58:50 [DEBUG] (f) container = org.codehaus.cargo.maven2.configuration.Container@5d97da5f build 02-Jan-2013 14:58:50 [DEBUG] (s) groupId = com.toyota.tme.sample build 02-Jan-2013 14:58:50 [DEBUG] (s) artifactId = deploytest-web build 02-Jan-2013 14:58:50 [DEBUG] (s) type = war build 02-Jan-2013 14:58:50 [DEBUG] (f) pingURL = http://localhost:10000/deploytest-web/ping.html build 02-Jan-2013 14:58:50 [DEBUG] (f) pingTimeout = 1000 build 02-Jan-2013 14:58:50 [DEBUG] (f) deployables = [AbstractDependency{ groupId=com.toyota.tme.sample, artifactId=deploytest-web, type=war, classifier=null }] build 02-Jan-2013 14:58:50 [DEBUG] (f) localRepository = id: local build 02-Jan-2013 14:58:50 url: file:///opt/cie/data/maven/repository/ build 02-Jan-2013 14:58:50 layout: none build 02-Jan-2013 14:58:50 build 02-Jan-2013 14:58:50 [DEBUG] (f) pluginVersion = 1.3.1 build 02-Jan-2013 14:58:50 [DEBUG] (f) project = MavenProject: com.toyota.tme.sample:deploytest-deploy:2.0-SNAPSHOT @ /opt/bamboo-agent-4.1/xml-data/build-dir/DEPLOY-JETTYTESTDEPLOY-JOB1/pom.xml build 02-Jan-2013 14:58:50 [DEBUG] (f) repositories = [ id: nexus build 02-Jan-2013 14:58:50 url: http://sunciep01/nexus/content/groups/tme build 02-Jan-2013 14:58:50 layout: default build 02-Jan-2013 14:58:50 snapshots: [enabled => true, update => always] build 02-Jan-2013 14:58:50 releases: [enabled => true, update => daily] build 02-Jan-2013 14:58:50 ] build 02-Jan-2013 14:58:50 [DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@6c81d7e8 build 02-Jan-2013 14:58:50 [DEBUG] (f) skip = false build 02-Jan-2013 14:58:50 [DEBUG] (f) wait = false build 02-Jan-2013 14:58:50 [DEBUG] -- end configuration --

The monitor seems to use the wrong timeout value (it comes from the container rather than the pingTimeout value)

1 2 3 4 5 6 7 build 02-Jan-2013 14:59:04 [DEBUG] [talledLocalContainer] spawned process java.lang.UNIXProcess@76701229 build 02-Jan-2013 14:59:04 [DEBUG] [URLDeployableMonitor] Checking URL [http://localhost:10000/cargocpc/index.html] for status using a timeout of [180000] ms... build 02-Jan-2013 14:59:04 [DEBUG] [URLDeployableMonitor] URL [http://localhost:10000/cargocpc/index.html] is not responding: -1 java.net.ConnectException: Connection refused ... build 02-Jan-2013 14:59:18 [DEBUG] [URLDeployableMonitor] URL [http://localhost:10000/cargocpc/index.html] is responding... build 02-Jan-2013 14:59:18 [DEBUG] [URLDeployableMonitor] Notifying monitor listener [org.codehaus.cargo.container.spi.deployer.DeployerWatchdog@79e9f5b1] build 02-Jan-2013 14:59:18 [INFO] [talledLocalContainer] Jetty 7.x started on port [10000]

Either that or we are misunderstanding the point of pingURL / pingTimeout.

Could it be that the cargocpc/index.html takes precedence over our configuration?
0

Status

Assignee

Savas Ali Tokmen

Reporter

mond raymond

Components

Fix versions

Affects versions

1.3.1

Priority

Major