Java | Debugging

-

In the day-to-day life of a programmer, most of the time is spent in debugging. Writing a code can be easy, but fixing a bug can be a nightmare. The java applications can be debugged to check why application is not behaving as expected. 

To debug a Spring boot application we have to start application in debug mode. The Spring boot application we created in last post can be debugged as follows - 

Intellij Idea - 


Once the application is started you can add debug points in code by double-clicking on desired line.


As soon as we hit a request, it can be seen that the code execution stopped where debug is added. We check the variables in the right hand side of debug mode. This is useful to check what value is being set. It also has options to mute debug points if we want to continue with normal execution etc. 


Most of the IDEs support the Evaluate function. To check some logic, we can right click on code and select Evaluate Expression option where we can add custom code to check values logic etc. This is useful where your code is throwing error/exception which is not getting printed in logs due to incorrect exception handling. Such exceptions/error as ClassDefNotFound can be easily caught.

Hot Swap

If we found issue in our code and want to check if that works or not, we can do hot swap to apply class file to deployed application. In Intellij we have to click on Compile and reload option which will compile class file again and HotSwap.


In the real scenario there might be a corner case causing an issue which can be caught in debug mode. It is always recommended writing a unit test around coding to minimize code errors.

In case of deployed applications, the developer can always use remote debugging. 


In the Run configuration the Remote JVM Debug configuration can be added. We have to provide the debug port and host of the remote deployed application.

Spring - 

For Spring Boot Application we can add below arguments to application startup to attach debug port. The debug we used in IDE also uses this arguments while starting application. 

Use below command to start Spring boot application in debug mode from command line.

We can always change debug port by address=desire_port

WebLogic -

We can append below argument in WebLogic server start script to debug applications deployed.

Tomcat - 

Use below command to in case application is deployed in tomcat.


Comments

Post a Comment

Popular posts from this blog

Spring | Using TIBCO EMS with Spring framework

-
TIBCO EMS can be use with Spring Framework to support message publishing and subscription. Spring provides JMS template to send JMS messages and @JmsListener/ MessageListener to subscribe it. Steps 1 : Create new project in eclipse or IntelliJ Idea Create new project with Spring dependency. We can use maven to add all required libs for this project. Maven takes care of adding referred java libs to build path. TIBCO JMS jars need to be added to build path. Pom.xml will be as follows. As you can see in above pom file we have added TIBCO JMS and Spring JMS dependency. Step 2 : Create JMS bean configuration file(Jms-conf.xml) Next we will create bean configuration file. It will set JNDI and JMS properties. We can use same JMS listener class to subscribe multiple queues and topics. Spring bean configuration take care of JMS transport setup. Env variables values can be provided via properties file. Step 3 : Create JMS Queue/Topic sender and Listner In above cod
Read more

TIBCO | For Loop - Accumulate output

-
Image
In this post we will check how TIBCO for loop works. TIBCO provides Group Activity to iterate over processes or activities. Loops can be different types eg. For Loop, While util loop, if loop, repeat on error etc. TIBCO group can loop over sub-process and accumulate output in end activity to be used by next activities. TIBCO For loop with Accumulate output repeats over process/activity and return output of each iteration in output activity. This is helpful where we want to call sub-process repeatably with different input parameters and store each output in some variable.
Read more

TIBCO | JNDI Server & JMS Instance creation

-
Image
In this post we will be creating TIBCO JNDI server and other instance pointed to JNDI server. First lets see what is mean by JNDI. It is   Java API for a directory service that allows Java software clients to discover and look up data and objects via a name. TIBCO EMS uses JNDI concept to lookup for EMS objects and its relations in messaging service. While developing enterprise level TIBCO solution it is advise or say standard practice to create one JNDI server(also one backup JNDI server) and other instance servers according to the functionality or domains. In this tutorial we will be creating one JNDI server and two domain servers.
Read more