Skip to content
This repository has been archived by the owner on Nov 28, 2022. It is now read-only.

SVT: Build failure with Appsody Open Liberty #2455

Open
sujeilyfonseca opened this issue Mar 11, 2020 · 29 comments
Open

SVT: Build failure with Appsody Open Liberty #2455

sujeilyfonseca opened this issue Mar 11, 2020 · 29 comments
Labels
area/appsody Appsody in Codewind kind/bug priority/hot

Comments

@sujeilyfonseca
Copy link

Codewind version: 0.10.0
OS: VM with Windows 10

IDE extension version: 0.10.0
IDE version: 1.42.0

Build date: 2020-03-10-12:22:59
build_info.url=https://download.eclipse.org/codewind/codewind-vscode/0.10.0/7
build_info.che.SHA-1=a1bfcb9274bc5365489e96596ab2faea4dc1678f
build_info.SHA-1=90663a8ff7ba33857f163016cb5c813df2d2e35d

Description: After migrating from Codewind 0.9.0 to 0.10.0, I got a build failure twice with an Appsody Open Liberty project. The first time was immediately after migration. After that, I triggered a manual build, and the project seemed to build. However, after starting and stopping Codewind, I again got a build failure with the same project. All other projects behave as expected.

For a user, it can be confusing that the status of the project is [Stopped] [Build Succeeded] when that is not correct.

Screen Shot 2020-03-11 at 10 02 26 AM

Logs:
cw-appsody-open-liberty-1.txt
cw-appsody-open-liberty-2.txt
codewind-pfe.txt
codewind.log
filewatcherd-1.log

@jagraj
@makandre
Copy link
Contributor

makandre commented Mar 11, 2020 •
edited
Loading

In both cases I see

[Container] [INFO] CWWKM2010I: Searching for CWWKF0011I: in /opt/ol/wlp/usr/servers/defaultServer/logs/messages.log. This search will timeout after 120 seconds.
[Container] [INFO] CWWKM2013I: The file /opt/ol/wlp/usr/servers/defaultServer/logs/messages.log being validated does not exist.
...
[Container] [INFO] CWWKM2011E: Timed out searching for CWWKF0011I: in /opt/ol/wlp/usr/servers/defaultServer/logs/messages.log.

And then the Liberty server is stopped after that

@makandre
Copy link
Contributor

@sujeilyfonseca Does this happen on a new openliberty project?

@sujeilyfonseca
Copy link
Author

I can reproduce the problem intermittently with new Appsody Open Liberty projects. They can build fine the first time, but they might not after stopping and starting Codewind.

Here is an example of the mentioned scenario:

cw-appsody-open-liberty-0.10.0.txt

@jgwest jgwest added area/appsody Appsody in Codewind area/iterative-dev Related to building and deploying applications (AKA "Turbine") labels Mar 11, 2020
@jagraj
Copy link

jagraj commented Mar 11, 2020

Looks like this issue exists in Codewind 0.9.0 as well. I have CW 0.9 workspace and tried to reproduce this problem and this seems to be intermittent problem. One of my appsody open liberty project built and started fine. I created another appsody open liberty project and it failed to build and it also made my first project to fail as well. Looks like something is not right with this stack. We have seen similar issues with Appsody Eclipse Microprofile projects as well in the previous releases and we are seeing same behavior with open liberty stacks as well.

We can consistently reproduce this problem in both Codewind 0.9 and 0.10 releases. Can we make this as "stopship".? Do you think this is Appsody or Codewind problem.?

[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 2 minutes, 38.403 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  05:04 min
[Container] [INFO] Finished at: 2020-03-11T18:25:51Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 120 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

@makandre
Copy link
Contributor

Fairly certain this is an issue in the appsody stack.

@jagraj
Copy link

jagraj commented Mar 12, 2020

Making this as stopship and we need to investigate with appsody team why this stack fails intermittently.

@jagraj
Copy link

jagraj commented Mar 12, 2020

/priority stopship

@makandre
Copy link
Contributor

@jagraj @sujeilyfonseca could I have access to your machines to investigate? So far I have not been able to reproduce it

@sujeilyfonseca
Copy link
Author

@makandre, I'll share my machine credentials with you via Slack. I currently have 4 out of 5 Appsody Open Liberty projects with build failures.

Screen Shot 2020-03-12 at 9 52 52 AM

@makandre
Copy link
Contributor

It's really a timing issue, it looks like the stack waits 120 seconds for the CWWKF0011I message to appear in the log. That message is:

CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 104.223 seconds.

@makandre
Copy link
Contributor

There maybe an easy workaround actually, in the project's pom.xml file, look for:

<serverStartTimeout>120</serverStartTimeout>

You can try increasing the timeout there

@sujeilyfonseca
Copy link
Author

My projects built after increasing the timeout to 180:

Screen Shot 2020-03-12 at 10 32 39 AM

However, they stopped again with same errors:

[Container] [INFO] [WARNING ] CWWKE1102W: The quiesce operation did not complete. The server will now stop.
[Container] [INFO] [WARNING ] CWWKE1105W: 1 runtime updates did not complete during the quiesce period. 
[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 4 minutes, 23.98 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  09:40 min
[Container] [INFO] Finished at: 2020-03-12T14:34:33Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 180 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

[Container] [INFO] [WARNING ] CWWKE1102W: The quiesce operation did not complete. The server will now stop.
[Container] [INFO] [WARNING ] CWWKE1105W: 1 runtime updates did not complete during the quiesce period. 
[Container] [INFO] [AUDIT   ] CWPKI0803A: SSL certificate created in 114.996 seconds. SSL key file: /opt/ol/wlp/usr/servers/defaultServer/resources/security/key.p12
[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 4 minutes, 32.133 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  09:53 min
[Container] [INFO] Finished at: 2020-03-12T14:34:34Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 180 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

[Container] [INFO] [WARNING ] CWWKE1102W: The quiesce operation did not complete. The server will now stop.
[Container] [INFO] [WARNING ] CWWKE1105W: 1 runtime updates did not complete during the quiesce period. 
[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 4 minutes, 19.982 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  09:49 min
[Container] [INFO] Finished at: 2020-03-12T14:34:24Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 180 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

[Container] [INFO] [WARNING ] CWWKE1102W: The quiesce operation did not complete. The server will now stop.
[Container] [INFO] [WARNING ] CWWKE1105W: 1 runtime updates did not complete during the quiesce period. 
[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWPKI0803A: SSL certificate created in 134.909 seconds. SSL key file: /opt/ol/wlp/usr/servers/defaultServer/resources/security/key.p12
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 4 minutes, 26.452 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  09:48 min
[Container] [INFO] Finished at: 2020-03-12T14:34:27Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 180 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

Therefore, I proceeded to increase the timeout to 260. This caused the projects to build and start. However, the projects have a [Running] [Build Succeeded] status, but don't appear to be actually running.

Screen Shot 2020-03-12 at 11 03 25 AM

Screen Shot 2020-03-12 at 11 03 49 AM

@makandre
Copy link
Contributor

I would recommend trying with a large timeout (say 600 = 10 mins) just so we can narrow down whether the apps can indeed start.

Do these app contained any custom code or are they largely unmodified from when they were created by Codewind?

Re the Open Liberty landing page you see, the fact it shows as [Running] means the /health endpoint is up (can you verify by going to it?) and that by definition means the app is running. I have seen cases when the app doesn't serve up the custom landing page but that again is an issue with the the stack itself (try modifying the src/main/webapp/index.html file and see if that would trigger the page to be served up)

@sujeilyfonseca
Copy link
Author

Increasing the time by 600 (10 minutes) seemed to work:

Screen Shot 2020-03-12 at 12 31 47 PM

Screen Shot 2020-03-12 at 12 30 53 PM

These are simple templates. They don't have any custom code or changes.

We should either aim to increase the default timeout for users or document the workaround.

@makandre
Copy link
Contributor

I agree, we should document the workaround. I'll put up a PR for this.

Do we agree that this is not a stopship then?

@makandre makandre mentioned this issue Mar 12, 2020
Merged
@makandre
Copy link
Contributor

Doc PR: eclipse-archived/codewind-docs#484

@sujeilyfonseca
Copy link
Author

sujeilyfonseca commented Mar 12, 2020 •
edited
Loading

During a call with @sghung, @makandre, and @jagraj, I was able to reproduce a similar scenario in MacOS:

Screen Shot 2020-03-12 at 2 42 41 PM

[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 2 minutes, 42.032 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  04:29 min
[Container] [INFO] Finished at: 2020-03-12T18:32:47Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 120 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 2 minutes, 36.994 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  04:21 min
[Container] [INFO] Finished at: 2020-03-12T18:32:39Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 120 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

[Container] [INFO] [AUDIT   ] CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 134.677 seconds.
[Container] [INFO] [ERROR   ] CWWKZ0002E: An exception occurred while starting the application starter-app. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.util.concurrent.RejectedExecutionException: CWWKE1202E: A task cannot be submitted because the executor managedExecutorService[DefaultManagedExecutorService] (concurrencyPolicy[defaultConcurrencyPolicy]) has been shut down.
[Container] [INFO] [AUDIT   ] CWWKE0036I: The server defaultServer stopped after 2 minutes, 20.256 seconds.
[Container] [INFO] Server defaultServer stopped.
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] BUILD FAILURE
[Container] [INFO] ------------------------------------------------------------------------
[Container] [INFO] Total time:  04:17 min
[Container] [INFO] Finished at: 2020-03-12T18:33:21Z
[Container] [INFO] ------------------------------------------------------------------------
[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 120 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]
[Container] [ERROR] 
[Container] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[Container] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[Container] [ERROR] 
[Container] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[Container] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[Container] [INFO] CWWKM2001I: Invoke command is [/opt/ol/wlp/bin/server, stop, defaultServer].
[Container] [INFO] 
[Container] [INFO] Stopping server defaultServer.
[Container] [INFO] Server defaultServer is not running.
[Container] + set +x
[Container] The file watcher is not running because no APPSODY_RUN/TEST/DEBUG_ON_CHANGE action was specified or it has been disabled using the --no-watcher flag.
Closing down development environment.

@jagraj
Copy link

jagraj commented Mar 12, 2020

I and Steven tried to reproduce this problem outside of Codewind and got into this problem where Open liberty, Spring boot both of the stacks failed due to this issue (appsody/appsody#912). We need this issue to be resolved to isolate the problem between Codewind and Appsody.

C:\java-spring-boot>appsody init java-spring-boot2
Checking stack requirements...
Docker requirements met
Appsody requirements met
Running appsody init...
Downloading java-spring-boot2 template project from https://github.com/appsody/stacks/releases/download/java-spring-boot2-v0.3.27/incubator.java-spring-boot2.v0.3.27.templates.default.tar.gz
Download complete. Extracting files from C:\java-spring-boot\java-spring-boot2.tar.gz
Setting up the development environment
Your Appsody project name has been set to java-spring-boot
Pulling docker image docker.io/appsody/java-spring-boot2:0.3
Running command: docker pull docker.io/appsody/java-spring-boot2:0.3
0.3: Pulling from appsody/java-spring-boot2
Digest: sha256:7e3350761cbc1f926478b6cf9a362cf7735d34653031c2314c2f625049346a91
Status: Image is up to date for appsody/java-spring-boot2:0.3
docker.io/appsody/java-spring-boot2:0.3
Running command: docker run --rm --entrypoint /bin/bash docker.io/appsody/java-spring-boot2:0.3 -c "find /project -type f -name .appsody-init.bat"
Extracting project from development environment
Running command: docker run --name java-spring-boot-extract -v C:/java-spring-boot/.:/project/user-app -v C:/Users/Administrator/.m2/repository:/mvn/repository --entrypoint /bin/bash docker.io/appsody/java-spring-boot2:0.3 -c "cp -rfL /project /tmp/project"
Running command: docker rm java-spring-boot-extract -f
[Warning] Ignoring container remove error Error running docker command: exit status 1
[Warning] The stack init script failed: Error attempting to run copy command cp -rfL /project /tmp/project on image docker.io/appsody/java-spring-boot2:0.3: exit status 125
[Warning] Your local IDE may not build properly, but the Appsody container should still work.
[Warning] To try again, resolve the issue then run `appsody init` with no arguments.
Successfully initialized Appsody project with the java-spring-boot2 stack and the default template.

C:\java-spring-boot>
C:\java-spring-boot>
C:\java-spring-boot>appsody run
Running development environment...
Pulling docker image docker.io/appsody/java-spring-boot2:0.3
Running command: docker pull docker.io/appsody/java-spring-boot2:0.3
0.3: Pulling from appsody/java-spring-boot2
Digest: sha256:7e3350761cbc1f926478b6cf9a362cf7735d34653031c2314c2f625049346a91
Status: Image is up to date for appsody/java-spring-boot2:0.3
docker.io/appsody/java-spring-boot2:0.3
Running command: docker run --rm -p 35729:35729 -p 5005:5005 -p 8080:8080 -p 8443:8443 --name java-spring-boot-dev -v C:/java-spring-boot/.:/project/user-app -v C:/Users/Administrator/.m2/repository:/mvn/repository -v appsody-controller-0.3.4:/.appsody -t --entrypoint /.appsody/appsody-controller docker.io/appsody/java-spring-boot2:0.3 "--mode=run"
[Container] docker: Error response from daemon: file does not exist.
[Container] See 'docker run --help'.
[Error] Error in 'appsody run': exit status 125

@sujeilyfonseca
Copy link
Author

@sghung, I added the log errors to my previous comment.

@rajivnathan rajivnathan removed the area/iterative-dev Related to building and deploying applications (AKA "Turbine") label Mar 12, 2020
@rajivnathan
Copy link
Contributor

Removing the iterative-dev label since this seems to be an appsody specific issue

@makandre
Copy link
Contributor

If appsody/appsody#912 is blocking test on Windows, then test on Mac (since #2455 (comment) mentions it is reproduced there)

In any case it's actually easy to make this error happen by going the opposite way, i.e. reducing the timeout value. I set it to 10 seconds and my server doesn't start within that time, in or out of Codewind (although I'm not sure what this proves).

@makandre
Copy link
Contributor

I should also point out, the message from Liberty also states that the user should consider increasing the serverStartTimeout value as a way to get around this:

[Container] [ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.2:dev (default-cli) on project starter-app: Unable to verify if the server was started after 120 seconds.  Consider increasing the serverStartTimeout value if this continues to occur. -> [Help 1]

@jagraj
Copy link

jagraj commented Mar 12, 2020

@makandre @sghung
Looks like we are able to reproduce this problem in both Windows and Mac intermittently and we should increase this default timeout and users will not see this problem frequently.

We already documented workaround and error message says to increase timeout and this is no longer "stopship" issue for Codewind 0.10.0 release. We should work with appsody team and increase this default timeout value.

@sghung
I am not a committer, can you remove stopship flag and set priority as "hot".?

@malincoln
Copy link

@jagraj I update the labels for you.

@makandre
Copy link
Contributor

I opened appsody/stacks#717 to see if we can have the default timeout value increased

@scottkurz
Copy link

@jagraj the issue here #2455 (comment)

Running command: docker run --rm -p 35729:35729 -p 5005:5005 -p 8080:8080 -p 8443:8443 --name java-spring-boot-dev -v C:/java-spring-boot/.:/project/user-app -v C:/Users/Administrator/.m2/repository:/mvn/repository -v appsody-controller-0.3.4:/.appsody -t --entrypoint /.appsody/appsody-controller docker.io/appsody/java-spring-boot2:0.3 "--mode=run"
[Container] docker: Error response from daemon: file does not exist.
[Container] See 'docker run --help'.
[Error] Error in 'appsody run': exit status 125

looks like issue: appsody/appsody#912

I have a workaround in a PR...I'll ask again if they can merge it. (I also have a Windows binary if you want to ping me).

@sghung
Copy link
Contributor

sghung commented Mar 13, 2020

@jagraj for the windows VM I have, I cannot upgrade to the latest docker (it won't allow me to due to the OS), so I couldn't reproduce appsody issue 912, as I was able to get my open liberty to run fine with appsody 0.5.9 when running the CLI.

@scottkurz
Copy link

@sghung thanks for the note. I'll ping the appsody/appsody committers to ask them to merge my fix soon.

@scottkurz
Copy link

@sghung @jagraj ..the Windows fix I mentioned is now available in v0.6.0:
https://github.com/appsody/appsody/releases/tag/0.6.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/appsody Appsody in Codewind kind/bug priority/hot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@jagraj @scottkurz @jgwest @sghung @makandre @rajivnathan @malincoln @sujeilyfonseca @codewind-bot