Avoid Running Long processes when consuming Kafka Messages

TODO. :Add information

Spring Boot with MongoDB

 Sample spring-boot project with mongo db integration is available at https://github.com/akashmahakode/mongodb-demo

Spring Boot With Kafka Producer and Consumer

Sample spring-boot project with kafka integration is available at https://github.com/akashmahakode/kafka-demo 

Getting Objects in Aspects

 import lombok.extern.slf4j.Slf4j;

import org.aspectj.lang.annotation.After;

import org.aspectj.lang.annotation.Aspect;

import org.springframework.stereotype.Component;

/**

 * Aspect to log the message when object is saved

 */

@Slf4j

@Aspect

@Component

public class MyLoggerAspect {

// "obj" is object_which_is_saved_in_save_method i.e in com.foo.save(*)

@After("execution(* com.foo.save(*)) && args(obj)")

public void logAfterSavingTheObject(CustomObject obj) {

log.info("Logging after the CustomObject is saved, id : {}", obj.getId())

}

}

DynamoDB: InvalidSignatureException : The request signature we calculated does not match the signature you provided

In one of our application, while connecting to DynamoDB, our application was getting following exception-

com.amazonaws.services.dynamodbv2.model.AmazonDynamoDBException:
The request signature we calculated does not match the signature you provided.
Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

There was no deployment on our side and we were surprised to see this issue. This issue was not happening for all the requests to DynamoDB. So, we were not sure where is the problem coming from.

There are already various posts to troubleshoot this exception-
1. https://docs.aws.amazon.com/general/latest/gr/signature-v4-troubleshooting.html
2. Problem with the skewed clocks on the server.
3. Access token not valid.

We tried all the steps as suggested by AWS tech support, various posts on google or stack overflow but none of these worked out.

So, we enabled the debug logs and analyzed the POST requests going to DynamoDB. After going through the request payload and headers, we found out that -
1. All failed requests have extra header "lets-say-xyz_now" which was passed to DynamoDB request.
2. All successful requests did NOT have extra header "lets-say-xyz_now" in the request to DynamoDB.

So, AWS was using this extra header in the signing algorithm which caused this exception.

One of our upstream services passed this header which got passed to DynmoDB. So, we removed the extra header and everything started working again.

Another suspect is underscore(_) present in the header. Some blogs suggest that nginx drops headers with underscore. http://nginx.org/en/docs/http/ngx_http_core_module.html#underscores_in_headers

Starting Jenkins

Here is the simple command to start jenkins server. Download the .war file from Jenkins website
and run command below-
$ nohup java -Xms1024m  -Xmx8192m -XX:MaxPermSize=1024M -XX:+UseParallelOldGC -XX:ParallelGCThreads=4 -XX:+HeapDumpOnOutOfMemoryError  -Dhudson.util.ProcessTree.disable=true -Djava.awt.headless=true -DHUDSON_HOME=. -jar jenkins.war --httpPort=8585 

XULRunner issues on eclipse 3.6(Helios)

http://www-01.ibm.com/support/docview.wss?uid=swg21592804