Issues with Resolutions

 

1.
Situation / Task (Explain the situation or task so others understand the context):
Partition Queue is block (for emails/ for any events) due to one bad event.
Action (Give details about what you or another person did to handle the situation):
Raise the alert and log the exception
adding Feature flag for logging or catching the exception.
Result (Describe what was achieved by the action and why it was effective):
Now the partition queue released all blocked event, and it seems, no blocking queue.

2.
Situation / Task (Explain the situation or task so others understand the context):
Few messages in the queue are missing
Action (Give details about what you or another person did to handle the situation):
Previously, we have added event specific multiple listeners, now we maintained in a single endpoint listener and once we got the events, based on the event, split those events into multiple handlers.
Result (Describe what was achieved by the action and why it was effective):
Now able to process all messages in the queue.

 

3.
Situation / Task (Explain the situation or task so others understand the context):
Idempotent issue
Action (Give details about what you or another person did to handle the situation):
Maintained the key in cache and validating (implemented the logic for idempotent issues.)
Filtering the duplicates
Result (Describe what was achieved by the action and why it was effective):
Now the records are capturing as resilient.

4.
Situation / Task (Explain the situation or task so others understand the context):
Alignment Issue in UX (browser specific)
Action (Give details about what you or another person did to handle the situation):
It seems, 1 day task but after revamp the complete block of html div, then the issue is fixed.
Result (Describe what was achieved by the action and why it was effective):
In all browsers, it looks good

5.
Situation / Task (Explain the situation or task so others understand the context):
ETL performance issues, each job is executing more than expected time.
Action (Give details about what you or another person did to handle the situation): Result (Describe what was achieved by the action and why it was effective):

 

6.
Situation / Task (Explain the situation or task so others understand the context):
While using @Async, @Transactional, @Cacheable annotations, Its not working as expected

Action (Give details about what you or another person did to handle the situation):

Result (Describe what was achieved by the action and why it was effective):
Those annotations are Spring specific
It will not applicable for private method and calling method is in same class
Because, it will create proxy based, so while instantiate the bean, the proxy intercepts before / after and add few functionalities.

7. Situation / Task (Explain the situation or task so others understand the context):
FIS

Action (Give details about what you or another person did to handle the situation):

Result (Describe what was achieved by the action and why it was effective):