[
https://issues.apache.org/jira/browse/FINERACT-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118443#comment-17118443
]
Petri Tuomola commented on FINERACT-1011:
-----------------------------------------
[~awasum] - I haven't seen this myself. But you're right that it looks like the
timeout value for the container startup was not sufficient for some reason.
You can increase the timeout by using the startStopTimeout property for the
cargo plugin configuration. But since I can't reproduce this issue on my
machine, I can't check if that would resolve your issue.
And yes, if the port is in use then probably the previous instance has been
left running - and killing it should help.
> Execution failed for task ':cargoStartLocal' when running IntegrationTest
> locally
> ---------------------------------------------------------------------------------
>
> Key: FINERACT-1011
> URL: https://issues.apache.org/jira/browse/FINERACT-1011
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Awasum Yannick
> Assignee: Awasum Yannick
> Priority: Major
> Fix For: 1.4.0
>
>
> When you run ./gradlew clean integrationTest locally (using Ubuntu 16.04,
> MySQL 5.7 on Docker), you get the error:
> Execution failed for task ':cargoStartLocal'.
> > org.codehaus.cargo.container.ContainerException: Deployable
> > [https://localhost:8443/cargocpc/index.html] failed to finish deploying
> > within the timeout period [120000]. The Deployable state is thus unknown.
> If you try to run again after the process stops you get this error:
> Execution failed for task ':cargoStartLocal'.
> > org.codehaus.cargo.container.ContainerException: Port number 8443 (defined
> > with the property cargo.servlet.port) is in use. Please free it on the
> > system or set it to a different port in the container configuration.
> It seems the timeout is short for some computers (maybe slower computers) so
> Cargo Tomcat does not start within timeout. Then on second try to run
> integration Tests, the tomcat instance is still running in the background and
> this cuases the second problem?
> I am using Ubuntu 16.04, MySQL 5.7 on Docker. RAM is 16GB. This machine is i7
> (8 CPUS). Using HDD not SSD(Maybe this is the problem) or can we do something
> to make this better? [~vorburger] or [~ptuomola] or anyone else, do you have
> any ideas, you seen this?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
