> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/spring/spring-features/spring-aop/after-finally-advice.md).
# After (finally) Advice
After (finally) advice is executed regardless of whether the target method completes successfully or throws an exception. It allows to perform cleanup or resource release actions. Some of the use cases are described below.
**Transaction Management**: It can be used for committing or rolling back database transactions after method execution, ensuring data consistency. Helpful to add logic for releasing locks or other resources acquired during transactional operations.
**Logging**: Useful in logging method completion messages or status updates for tracking and debugging purposes. Cleaning up temporary files or resources used during method execution.
**Sample Example**
Scenario 1: Logging the method arguments.
Create Aspect class
***LoggingAspect.java***
```java
package org.example.logging;
import lombok.extern.slf4j.Slf4j;
import org.aspectj.lang.JoinPoint;
import org.aspectj.lang.annotation.After;
import org.aspectj.lang.annotation.Aspect;
import org.springframework.stereotype.Component;
@Slf4j
@Aspect
@Component
public class LoggingAspect {
private static final String AFTER_POINTCUT ="execution(* org.example.controller.*.*(..))";
@After(value = AFTER_POINTCUT)
public void logsErrors(JoinPoint joinPoint){
// Log the controller name
log.info("After - {}", joinPoint.getSignature().getName());
// Log the exception message
log.info("After - {}", joinPoint.getArgs());
}
}
```
Create controller class
```java
package org.example.controller;
import lombok.RequiredArgsConstructor;
import lombok.extern.slf4j.Slf4j;
import org.example.Model.InputData;
import org.example.Model.OutputData;
import org.example.service.DataService;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
@Slf4j
@RestController
@RequiredArgsConstructor
@RequestMapping("/data")
public class DataApi {
private final DataService dataService;
@PostMapping("/extract")
public ResponseEntity getData(@RequestBody InputData inputData) {
// Crafting some logic which can throw exception
if (inputData != null) {
throw new ArithmeticException("Throwing some exception");
}
log.info("Extracting Data");
return new ResponseEntity<>(
dataService.extractData(inputData),
HttpStatus.OK
);
}
}
```
{% hint style="info" %}
Note that logic is set to throw exception
{% endhint %}
Run the application, execute the API and observe the logs
Output
{% hint style="info" %}
Note: The code snippet given in this page is just for understanding and does not contain complete code. (For e.g. missing service class code snippet)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://www.pranaypourkar.co.in/the-programmers-guide/spring/spring-features/spring-aop/after-finally-advice.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.