Developing Spring Boot Application using Docker - Part 2

-
Hopefully you have now got your Spring Boot Application run inside the container. If you are not there yet, please visit Developing Spring Boot Application using Docker - Part 1 to go start.

There is one thing as an Architect on my daily job, I used to ask myself, if we run the application inside the container, how do we debug? How to view logs? How to triage issues on local?

The biggest of all is debugging the Spring Boot Application that is running inside the container.

Setting up Debugging environment

The concept of debugging any Java Based Application that is running inside the container can be done using the most common way is using remote debugging. Typically, whenever we wanted to debug applications that are running in a machine that is outside of our own, we use Remote Debugging. Most IDEs like Eclipse and IntelliJ ship with those capabilities.

The good news is, the setup required to get that started are fairly common. Lets see how to get that setup when running on docker.

To keep the running configuration from the debugging configuration, let us create new Dockerfile and a docker-compose.yml file.

Dockerfile_debug 



docker-compose-debug.yml file

Now you have your application setup to be run in DEBUG mode. To start the application in debug mode, we need to run the below command.

$ docker-compose -f docker-compose-debug.yml up -d --build


This will start our application in debugging mode. Now that we have that started in debugging mode, it is time to integrate it with our IDEs.

For now I will go over IntelliJ IDEA and Eclipse as once you have this figured out in these IDEs, other IDEs will follow a similar technique.

Setting up IntelliJ for Debugging

Open the Spring Boot project inside IntelliJ and open the Edit Configurations... that is located near the Run/Debug gears.


Now, select the Remote JVM Debug.


We could potentially leave the configuration as is if the port is configured as 5005. If you cannot use port 5005 for some other reason, we need to choose the appropriate port select here and update our Dockerfile_debug and docker-compose-debug.yml file to use your port.


Thats it! Open the Controller and on the file gutter of the editor enable the break point. Start the Remote JVM Debug configuration.

Once you have enabled the debugger point test the endpoint. This will open the debugger at the break point.

Setting up Eclipse for Debugging


Make sure to open the Spring Boot Application inside Eclipse. Click on the Debug Configurations... on the IDE.

Now add a new Configuration by selecting Remote Java Application.


Please ensure to match the configuration as shown below.

Key Configuration Items:
  • Project: Select your Spring Boot Project
  • Connection Type: Standard (Socket Attached)
  • Connection Properties:
    • Host: localhost
    • Port: 5005
Hit Apply and Start Debugging if you have started your Docker in debug mode.

Add a break point on your code and test it. Eclipse will request for you to switch to Debug Perspective and it that all you have to do to debug your Spring Boot Applications using Eclipse.


Shutting down Debugging Docker

Please use the below command to bring down the running docker containers.

$ docker-compose -f docker-compose-debug.yml down

Next Steps

Now that we are able to run the Spring Boot Application inside a Docker container, it is time for us to add additional layers like adding a database connection and building our images.

The ultimate problem Docker solves is 
It works on my computer
.
 Now, since we have dockerized the Spring Boot Development, we can think about moving our applications into Docker.

The code for this part can be found here: https://github.com/reflexdemon/docker-example/tree/part-2
If you like the blog, poke me on my Twitter @reflexdemon


























Comments

Post a Comment

Popular posts from this blog

Java SSL/TLS Testing Tool: Cipher Suite

-
Image
Recently I was reading about the TLS/SSL and Ciphers. I was also interested to read about the Ciphers that are provided out of the box with JDK. This looked to me like this is something we take it for granted and do not do our due diligence when talking about the Ciphers. We often times leave those topic to our organization's network and security team. From my experience, it is a topic that all the developers leave it to the Sr. Developers and then the Sr. Developers pass it on to the Management. Guess what? It is not a sweet topic to discussion. To break this kind of symptom, I have choose to make it simple and want everyone to understand the complexity and importance of knowing this. Lets get started Before we wet our hands here is some basic information that you will require to know, Word Meaning Protocol A defined set of rules and regulations that determine how data is transmitted in telecommunications and computer networking SSL
Read more

PWA: Building and publishing a PWA in 15ish minutes using Angular 5 and Service Worker

-
Image
Introduction Here is an express start to your first PWA with service workers and a 100% score from lighthouse. I have taken it as a challenge to be able to present it to you so that you may be able to put your first pwa "hello world" app in 15ish minutes. What is PWA? Progressive web apps (PWAs) take traditional web sites/applications — with all of the advantages the web brings — and add a number of features that give them many of the user experience advantages of native apps. This set of docs tells you all you need to know. - Source: https://developer.mozilla.org/en-US/Apps/Progressive If the above definition sounds interesting, then this is to get you kickstarted with PWA using Angular 5 and inspire you to build more PWAs. End of this post you should be able to build, host and publish a PWA and get motivated to read more about it. Ever since I read about PWAs It has intrested me like crazy. Before, you get excited about PWA, please look into the supported brow
Read more

Yarn and Angular-CLI

-
Background I have been thinking of a faster package management tool ever since I started using NPM (Node Package Manager). Please don’t mistake me having anything against NPM. I still love this package manager and I very much love the rich command-line that it came with. When it was created, it was really the leader and because of this NPM the whole JS world has seen a revolution. NPM surly was the spark to the revolution in the JS (Java Script) world. To make it clear for everyone why we needed a new package manager is because of the following challenges that we had with NPM, 1.      The Nested dependencies that was sometimes going in infinity loops. At times, it was impossible to delete files on the PC as the paths were too nested. 2.      Everything on the world had to depend on only one registry. https://www.npmjs.com/ 3.      Single threaded installation. The installation of the dependencies are single threaded. 4.      You are always expected to be online even i
Read more