Observability of the Java Virtual Machine

-
Image
The JVM is one of the most observable runtimes. It provides us lots of tools for troubleshooting a JVM application in production. 1. Thread observability Threads are how the JVM actually does work. When something is wrong in production, the symptom is almost always a thread: stopped, blocked, leaking etc. Thread dumps work on any JVM with no  instrumentation, no agents, no restarts. <Example project link with /threaddump endpoint>         // (1) Deadlock — two threads grab the same pair of locks in opposite order.         new Thread(() -> grab(LOCK_A, LOCK_B), "deadlock-A-then-B").start();         new Thread(() -> grab(LOCK_B, LOCK_A), "deadlock-B-then-A").start(); http://localhost:8080/actuator/threaddump To list the JVMS, we can use the command below. PS C:\observe-jvm> jps -lv 25296 jdk.jcmd/sun.tools.jps.Jps -Dapplication.home=C:\Program Files\Microsoft\jdk-21.0.3.9-hotspot -Xms8m -Djdk.module.main=...
Post a Comment

Fluent Interface Example in an Enterprise Integration Project

-
While working on an enterprise integration project about virtual bank payments, I utilized a simple fluent interface approach. The purpose of the code is creating strongly typed objects from a generic SMO (ServiceMessageObject) instance.

Note: In the context of IBM integration technologies, ServiceMessageObject represents the “message”. In our example, it represents a Web Service request.

Old Code:

if (paymentInfo.getDataObject("totalAmount") != null) {
  totalAmount = paymentInfo.getDataObject("totalAmount");
  
  DataObject totalAmount2 = totalAmount.getDataObject("totalAmount");
  if (totalAmount2.getBigDecimal("amount") != null) {
   parameters.setAmount(totalAmount2.getBigDecimal("amount"));
  }
  
  String currencyCode = totalAmount2.getString("currencyCode");
  parameters.setCurrencyCode(currencyCode);  
     
 }
 Byte numberOfInstallments = paymentInfo.getByte("numberOfInstallments");
 if (numberOfInstallments != null) {
  parameters.setNumberOfInstallments(numberOfInstallments);
 }

if (transactionInfo.size() != 0) {
  if (((DataObject) transactionInfo.get(0)).getString("orderID") != null) {
   parameters.setOrderId(((DataObject) transactionInfo.get(0))
     .getString("orderID"));
   if (((DataObject) transactionInfo.get(0))
     .getString("transactionID") != null) {
    parameters.setTransactionID(((DataObject) transactionInfo
      .get(0)).getString("transactionID"));
   }
 parameters.setBankRefId(((DataObject) transactionInfo.get(0)).getString("bankReferenceID"));
//...more


It is really painful to read and modify this code. But actually, what it does is really simple. It should look simple.

New Code:

parameters.setCreditCardNumber(body
  .getDataObject("paymentInfo")
  .getDataObject("creditCardInfo")
  .getString("creditCardNumber"));

parameters.setCreditCardExpiryMonth(body
  .getDataObject("paymentInfo")
  .getDataObject("creditCardInfo")
  .getByte("creditCardExpiryMonth"));

parameters.setAmount(body
  .getDataObject("paymentInfo")
  .getDataObject("totalAmount")
  .getDataObject("totalAmount")
  .getBigDecimal("amount"));

parameters.setTransactionID(body
  .getListItem("transactionInfo")
  .getString("transactionID"));

This is a simple example of an internal DSL. The point I want to stress is this: “Use internal DSLs whenever you need better readability, among other things.”
This simple refactoring helped us a lot to read/modify the code easier than before.

To implement the DSL, what I did is hiding some details in a class that I named DataObjectWrapper. This class contains IBM's DataObject:

public class DataObjectWrapper {

    private DataObject dataObject;
    public DataObjectWrapper getListItem(String string) {
  
 List list = dataObject.getList(string);
  
 if (list.size() != 0) 
  return new DataObjectWrapper((DataObject)list.get(0));
   
 return new NullDataObject();  
    }

    public DataObjectWrapper getDataObject(String field) {

 if (dataObject.getDataObject(field) != null)
             return new DataObjectWrapper(dataObject.getDataObject(field));

 return new NullDataObject();
    }

    public String getString(String field) {
 return dataObject.getString(field);
    }

    public Byte getByte(String field) {
 return dataObject.getByte(field);
    }
}


To support fluent statements, NullDataObject is an important abstraction:

public class NullDataObject extends DataObjectWrapper {
    @Override
    public DataObjectWrapper getDataObject(String string) {
 return new NullDataObject();
    }

    @Override
    public String getString(String field) {
 return null;
    }
    // ...
}

Comments

Post a Comment

Popular posts from this blog

The WeakReference class, monitoring memory leak and garbage collection in a Java application

-
Image
 Below is a Stack implementation that uses an internal resizeable array structure.  public class MyStack< T > implements Stack< T > { private static final int CAPACITY = 100 ; private Object[] array ; private int pos = 0 ; public MyStack () { this . array = new Object[ CAPACITY ] ; } @Override public void push ( T item) { if ( pos >= array . length / 2 ) { Object[] newArray = new Object[ pos * 2 ] ; System. arraycopy ( array , 0 , newArray , 0 , array . length ) ; array = newArray ; } array [ pos ++] = item ; } @Override public T pop () { if (isEmpty()) { throw new RuntimeException( "empty stack" ) ; } @SuppressWarnings ( "unchecked" ) T item = ( T ) array [ pos - 1 ] ; pos -= 1 ; return item ; } @Override @SuppressWarnings ( "unchecked" ) public T peek...
Read more

Simplescalar Simulator - Part 2: sim-outorder.c

-
sim-outorder implements a very detailed out-of-order issue superscalar processor with a two-level memory system and speculative execution support. This simulator is a performance simulator, tracking the latency of all pipeline operations. Let's have a look at SimpleScalar simulator's code related to iTLB. (Instruction Translation Lookaside Buffer) First, there are simulator options related to iTLB: /* register simulator-specific options */ void sim_reg_options(struct opt_odb_t *odb) { /* TLB options */ opt_reg_string(odb, "-tlb:itlb", "instruction TLB config, i.e., { |none}", &itlb_opt, "itlb:16:4096:4:l", /* print */TRUE, NULL); opt_reg_int(odb, "-tlb:lat", "inst/data TLB miss latency (in cycles)", &tlb_miss_lat, /* default */30, /* print */TRUE, /* format */NULL); } /* check simulator-specific option values */ void  sim_check_options(... ) { /* sim-outorder.c  line: 1098*/   /* u...
Read more

Notes on Java Performance

-
Performance monitoring, performance profiling and performance tuning are different activities. For example, monitoring is not an intrusive action but profiling is. Because it may be changing the responsiveness of the running application. User CPU utilization vs Kernel CPU utilization: The ideal situation is when Kernel CPU utilization is 0%. So ideally, all the CPU cycles must be spent on our application code. JVM just in time compiler performs dynamic optimizations. So it makes decisions while the program is running and generates native code with better performance. Java 1.0 was completely interpreted but beginning with Java 1.1.8, there was a just-in-time compiler. It was 8 times faster. After that, paralellizing the garbage collector was a huge improvement. There are hundreds of Java tuning flags. https://github.com/ScottOaks/JavaPerformanceTuning Boolean flags use this syntax: -XX:+FlagName enables the flag, and -XX:-FlagName disables the flag. 32 BIT VS 64 BIT Fr...
Read more