NGINX configure Websocket in NginX – how to make it available

In the proxy.conf file, at the top, write:

upstream websocket {
        server name_of_my_docker_container:8080;

map $http_upgrade $connection_upgrade {
        default upgrade;
        '' close;

server {...

Why this? The Websocket has a constantly open connection with the client. The communication lies above the http protocol. This why we need to enable an „upgrade“ of the connection.

This example addresses a name of a Docker container. It would work with any other url too.

server {
      location / {...
      location name_of_my_docker_container {
		rewrite name_of_my_docker_container/(.*) /$1  break;
		proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header X-NginX-Proxy true;
		proxy_ssl_session_reuse on;
		proxy_set_header Host $http_host;
		proxy_cache_bypass $http_upgrade;
		proxy_redirect off;
		proxy_set_header X-Forwarded-Proto "http";
		proxy_pass http://name_of_my_docker_container:8080;
                // These headers need to be set in order 
                // to enable the communication:
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "Upgrade";

		proxy_set_header Connection '';
		proxy_http_version 1.1;
		chunked_transfer_encoding off;
		proxy_buffering off;
		proxy_cache off;

Calculation Errors and Mistakes in Java – How to calculate correctly

This is a real world example on which money was lost by client. This was not explicable, but I managed to analyze and reconstruct the problem.

The Code you are about to see is NOT the production code, but my own reconstruction of it, with a means to show the problem.

    public void testWrong() {

        // GIVEN
        final Integer price = -595;
        final Integer someUnit = 90;

        // WHEN
        int multiplicationResult = price * someUnit;
        // = -53550

        Integer resultAmount = multiplicationResult / 100;
        // = -535
        // …Division failed,
        // decimal places ignored...

        // THEN
        assertTrue(resultAmount == -535);
        // Wrong. Correct: -536.

The specification on which the primitives and float are defined do not allow a correct calculation (mistake 1).

Although primitives cause the most trouble in calculation programming for many people, this example would have worked, if the return type of „multiplicationResult“ would be a double (mistake 2).

But experience shows that even these basics are quite often the main reason for calculation mistakes in Java, so I always recommend a certain way of calculating to avoid them, which I will show below.

public void testCorrect() {

        // GIVEN
        final Integer price = -595;
        final Integer someUnit = 90;
        // WHEN
        BigDecimal priceBD = new BigDecimal(price);
        BigDecimal someUnitBD = new BigDecimal(someUnit);
        BigDecimal hundred = new BigDecimal(100);

        BigDecimal multiplicationResult = priceBD.multiply(someUnitBD); // = -53550

        // = -535.5 - looks great.
        BigDecimal resultAmountBD = multiplicationResult.divide(hundred);

        final int noDecimalPlaces = 0;
        // rounding mode is vital to get a correct result
        final RoundingMode roundingMode = RoundingMode.HALF_UP;

        // do not forget to define the decimal places...0
        BigDecimal result = resultAmountBD.setScale(noDecimalPlaces, roundingMode);

        // THEN
        assertThat(result.toBigInteger().intValue(), equalTo(-536)); // Correct!


The Big Decimal is calculated by using a String representation. Calculation is done piece by piece. Thus, the specification of float and primitives in general cannot interfere and cause calculation mistakes through number spaces, computing practices of the CPU etc..

Standard IEEE 754 defines Exception Handling and number spaces. It defines, how float and double is processed. Floating Points are meant to approach a certain precision, but without being 100% accurate. It is equivalent to Math/Analysis lambda, which is marking a barrier to come close to, which is never really reached (infinite lambda for instance).

In Summary:

  • Division, multiplication must be done by using a wrapper like BigDecimal.
  • Decimal Places have to be defined
  • Rounding modes have to be defined
  • In case that multiple systems are calculating together (e.g. bank or any other financial institution or software), a contract has to be agreed on. The contract must state how many decimal places are to be used (retail does often use 3 decimal places but only shows 2 on the displays in the shelves). Also the rounding mode plays a vital role in calculation.
  • Never use primitives, even if you are sure that in ‚your specific case‘ it is sufficient
  • Also experienced programmers make these mistakes, which is why I am posting this in my Blog.

GHOST IN THE MACHINE – Thoughts on AI… Pt. I

The issue with Artificial Intelligence, AI, is, that it is in many cases not possible, to tell WHY a decision was made. If an autonomous car decides to collide with the young woman on the street instead of jamming into the bus, when a collision had become inevitable, it is not possible to tell WHY.

We have to move forward, strive to achieve and develop the AI further in order to bring humanity to the next level.
But as it is not possible to look up Code and see the „IF collisionInevitable THEN collideWithYoungWoman“ part anymore, we must be aware of the greater challenge which awaits.

We need to tackle questions of morale, ethics and responsibility. How much rights are granted to artificial minds?

There will be a moment in time on which we take the Turing Test and suddenly we will think that there are feelings inside the machine. Perhaps there are. How will we proceed from there?

if else condition with Java Lamba – Howto

//lambda Predicate
private static Predicate<HttpStatus> isErrorCode = (HttpStatus statusCode) -> (statusCode.is5xxServerError() || statusCode.is4xxClientError());

//your method
public static Mono<ClientResponse> getResponse(ClientResponse clientResponse) {
        if (isErrorCode.test(clientResponse.statusCode())) {

Do not forget to checkout the BiPredicate as well 😉

Why Spring Webflux is better than HttpClient – HowTo in Java

A lot of Boilerplate Code can be avoided.

AND: it is reactive, non-blocking.

Example (really, an example) – the ‚old way‘:

        HttpPost request = new HttpPost("");
        request.setHeader(HttpHeaders.ACCEPT, ContentType.APPLICATION_JSON.getMimeType());

        String json = someJsonConverter.toJson(someRequestDto);
        HttpEntity stringEntity = new StringEntity(json, ContentType.APPLICATION_JSON);

        try {
            CloseableHttpResponse response2 = httpclient.execute(request);

            if (HttpStatus.SC_CREATED != response2.getStatusLine().getStatusCode()) {
                //TODO eventually handle http statuus additionally
                return returnHandleAndDoNotThrow();
            SomeResponseDto responseDto = (SomeResponseDto) 
            return Optional.ofNullable(responseDto);
        } catch (IOException e) {
            return Optional.empty();;

The new way:

        Function<UriBuilder, URI> function = uriBuilder ->  
                .body(Mono.just(someDtoInstance), SomeDto.class)
//any errors, status codes are handled by a filter which you can define as follows:


I am using Spring Boot for this, so I do have a Config class.

import ...
import org.springframework.context.annotation.Bean;
import reactor.core.publisher.Mono;
import org.springframework.web.reactive.function.client.ExchangeFilterFunction;
import org.springframework.web.reactive.function.client.WebClient;
import org.springframework.context.annotation.Configuration;

public class WebClientConfig {

    //Create the Bean for Autowiring
    public WebClient webClient() {
        return WebClient.builder().filter(someStatusHandlingFilter()).build();
    //Handle status codes
    public static ExchangeFilterFunction someStatusHandlingFilter() {
        return ExchangeFilterFunction.ofResponseProcessor(clientResponse -> {
            if ((clientResponse.statusCode().is4xxServerError() 
                || clientResponse.statusCode().is5xxClientError())) {
                return clientResponse                        
                        .flatMap(errorBody -> {
                            return Mono.error(someExceptionToLog);
            } else {
                return Mono.just(clientResponse);


            <version>your latest version goes here</version>
            <version>your latest version goes here</version>

Java Stream Custom Collector – Howto

Sometimes the commonly available Collectors are not what we need.
Here is one example for a Singleton Custom Collector:

public static <T> Collector<T, ?, T> singleton() {
    return Collectors.collectingAndThen(
            Collectors.toList(), list -> {
                if (list.size() != 1) {
                    // or log and return nil
                    throw new CustomException();
                return list.get(0);

//and use it:
        .filter(elem -> elem.getExampleAttribute() == 0).collect(singleton());