Error running with the SDK and a dockerized database

Development
1

Hi all,

I ran into a new problem today trying to run an existing server with the SDK on my machine. I tracked it down to the fact that I configured my server to use an existing docker container for the DB. I’m not sure what needs to be done to fix this in the SDK code, but I was able to work around it by simply removing the “db.docker.container” property from my openmrs-server.properties. As long as you make sure your DB container is started up yourself, things work fine. Here is the error message I was seeing in case someone wants to look into it (or in case someone Googles for this issue):

Starting 'openmrs-21x' DB docker container...
[INFO] Downloading from openmrs-repo: http://mavenrepo.openmrs.org/nexus/content/repositories/public/org/openmrs/maven/plugins/openmrs-sdk-docker-maven-plugin/3.13.1/openmrs-sdk-docker-maven-plugin-3.13.1.pom
[INFO] Downloading from openmrs-bintray-repo: https://dl.bintray.com/openmrs/maven/org/openmrs/maven/plugins/openmrs-sdk-docker-maven-plugin/3.13.1/openmrs-sdk-docker-maven-plugin-3.13.1.pom
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/openmrs/maven/plugins/openmrs-sdk-docker-maven-plugin/3.13.1/openmrs-sdk-docker-maven-plugin-3.13.1.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.932 s
[INFO] Finished at: 2018-08-07T17:29:53-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.openmrs.maven.plugins:openmrs-sdk-maven-plugin:3.13.1:run-tomcat (default-cli) on project standalone-pom: Unable to execute mojo: java.lang.reflect.InvocationTargetException: Plugin org.openmrs.maven.plugins:openmrs-sdk-docker-maven-plugin:3.13.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.openmrs.maven.plugins:openmrs-sdk-docker-maven-plugin:jar:3.13.1: Could not transfer artifact org.openmrs.maven.plugins:openmrs-sdk-docker-maven-plugin:pom:3.13.1 from/to openmrs-repo (http://mavenrepo.openmrs.org/nexus/content/repositories/public): Remote host closed connection during handshake: SSL peer shut down incorrectly -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.766 s
[INFO] Finished at: 2018-08-07T18:29:53-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.openmrs.maven.plugins:openmrs-sdk-maven-plugin:3.13.1:run (default-cli) on project standalone-pom: Execution default-cli of goal org.openmrs.maven.plugins:openmrs-sdk-maven-plugin:3.13.1:run failed: Failed running Tomcat -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

Mike

1 Like
2

Thanks @mseaton for sharing!

@raff could you have any pointers in regards to where this needs to be fixed in the SDK?

3

@dkayiwa, were you able to reproduce the issue? It looks like some connectivity issue…

4

No i did not.

5

‘SSL peer shut down incorrectly’ seems an awful lot like the problems we had with older versions of JDK…

6

@cintiadr I agree, and that may well be the issue here. If I ever get back to investigating on my end and can confirm this I’ll post back here.

7

I am still waiting for you to post @mseaton

8

Haha. @willa - this was 3 years ago :slight_smile: Are you implying that you are now running into this issue?