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

Timeout property set on ant cargo task is not sent to Cargo daemon (servlet)

Description

It seems that the value set on the timeout property for the ant task is not being sent on the request to the cargo daemon and therefore the timeout used to start the server is always the container default.

Tested on versions: 1.5.0 and 1.6.3
Container Id: weblogic122x

How to reproduce:
Found out since I wanted to disable the timeout functionality due to another problem with the deployment of the cargocpc war, so I set the timeout to 0, but even after this the container start will fail when trying to send a request to the test page. While debugging the cargo daemon I saw that the timeout request parameter was not sent to the CargoDaemonServlet and the default was always used

Status

Assignee

Unassigned

Reporter

Cristina Hinojosa

Components

Affects versions

1.6.3
1.5.0

Priority

Minor