스프링부트 서비스 layer에서 @Transactional 작동 안하는 문제..

Question

현재 진행중인 스프링부트 restapi 토이프로젝트에서 서비스 layer에서 특정 메소드에 @Transactional 어노테이션을 사용하여 dirty checking으로 DB 수정을 하려고 하는데 기존에는 DB에서 불러온 Entity에 수정이 생기면 메소드가 종료될 때 수정사항이 있으면 자동으로 update쿼리가 생성되어 DB 수정이 이루어졌는데, 이것 저것 만지다보니 @Transactional 메소드가 작동하지 않습니다 ㅠㅠUserApiController@Slf4j @RestController @RequestMapping("/api/users") @RequiredArgsConstructor @Validated public class UserApiController{ private final UserService userService; private final EmailService emailService; private final RedisUtil redisUtil; @PostMapping("/password") public ResponseEntity updatePwd(@RequestBody @Valid PwdChangeReqDto reqDto, @AuthenticationPrincipal CustomUserDetails principal) { log.info("[실행] UserApiController.updatePwd"); if (principal == null) { throw new NullPointerException(ErrorCode.UNAUTHENTICATION_USER.getMessage()); } this.userService.updatePwd(reqDto, principal.getId()); return ResponseFormat.RESPONSE_OK; } }UserService@Slf4j @Service @RequiredArgsConstructor public class UserService { private final UserRepository userRepository; private final FollowRepository followRepository; private final PasswordEncoder passwordEncoder; private String PARAM_EMAIL = "email"; private String PARAM_UID = "uid"; private String PARAM_NICK = "nick"; private String PARAM_PWDCONFIRM = "afterPwdConfirm"; private String PARAM_ID = "id"; @Transactional(propagation = Propagation.REQUIRES_NEW, readOnly = false) public void updatePwd(PwdChangeReqDto reqDto, Long id) { log.info("[실행] updatePwd"); User user = userRepository.findById(id) .orElseThrow(() -> new CustomException(ErrorCode.NOTFOUND_USER)); user.updatePwd(new BCryptPasswordEncoder().encode(reqDto.getBeforePwd())); } }로그를 확인해보니 @Transactional 이 붙은 updatePwd 메소드가 실행되는 시점에 새로운 트랜젝션이 생성되어야 할 것 같은데 그렇지 않고 findById에 의한 JPA 트랜젝션이 생성되는 상황이고요..그런데 또 @Transactional을 UserApiContoller의 updatePwd에 붙이면 UserService의 updatePwd가 호출 될 때 readOnly = false의 새 트랜젝션이 생성되어 dirty checking이 정상적으로 진행되어 수정되기는 하나 제가 원하는 작업은 서비스단에서 @Transactional을 사용하는 것입니다. 서로 다른 Bean인 UserApiController에서 UserService를 호출하기 때문에 내부호출과 같은 문제점은 아닐거라는 생각이 드는데 원인이 뭘까요??아래는 로그입니다.2023-08-15T02:09:31.487+09:00 INFO 21312 --- [nio-8080-exec-1] c.e.w.controller.user.UserApiController : [실행] UserApiController.updatePwd 2023-08-15T02:09:31.487+09:00 INFO 21312 --- [nio-8080-exec-1] c.e.wechall.service.user.UserService : [실행] updatePwd 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.orm.jpa.JpaTransactionManager : Found thread-bound EntityManager [SessionImpl(925013769)] for JPA transaction 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.orm.jpa.JpaTransactionManager : Creating new transaction with name [org.springframework.data.jpa.repository.support.SimpleJpaRepository.findById]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT,readOnly 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.jdbc.datasource.DataSourceUtils : Setting JDBC Connection [HikariProxyConnection@227483378 wrapping conn1: url=jdbc:h2:~/wechall user=SA] read-only 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.h.e.t.internal.TransactionImpl : On TransactionImpl creation, JpaCompliance#isJpaTransactionComplianceEnabled == false 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.h.e.t.internal.TransactionImpl : begin 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.orm.jpa.JpaTransactionManager : Exposing JPA transaction as JDBC [org.springframework.orm.jpa.vendor.HibernateJpaDialect$HibernateConnectionHandle@a790211] 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.sql.exec : Skipping reading Query result cache data: cache-enabled = false, cache-mode = IGNORE 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Initializer list 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : com.example.wechall.domain.entity.user.User -> EntityResultInitializer(com.example.wechall.domain.entity.user.User)@492791612 (SingleTableEntityPersister(com.example.wechall.domain.entity.user.User)) 2023-08-15T02:09:31.488+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.SQL : select u1_0.id, u1_0.auth_date, u1_0.created_date, u1_0.email, u1_0.nick, u1_0.profile_image, u1_0.pwd, u1_0.refresh_token, u1_0.role, u1_0.social_id, u1_0.social_type, u1_0.uid from member u1_0 where u1_0.id=? Hibernate: select u1_0.id, u1_0.auth_date, u1_0.created_date, u1_0.email, u1_0.nick, u1_0.profile_image, u1_0.pwd, u1_0.refresh_token, u1_0.role, u1_0.social_id, u1_0.social_type, u1_0.uid from member u1_0 where u1_0.id=? 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.hibernate.orm.results.loading.entity : (EntityResultInitializer) Hydrated EntityKey (com.example.wechall.domain.entity.user.User): 30 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.hibernate.orm.results.loading.entity : (EntityResultInitializer) Created new entity instance [com.example.wechall.domain.entity.user.User#30] : 163588631 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [1] - [null] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [2] - [2023-08-15T01:48:29.299424] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [3] - [null] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [4] - [test] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [5] - [null] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [6] - [$2a$10$1d7TiRH.WA9J3PGrCuUEjOieV7HRmBVwHG8GP0X2aJN/MhMhLUcHK] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [7] - [eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJSZWZyZXNoVG9rZW4iLCJleHAiOjE2OTMyNDE1Njl9.efHy1w2Nu3_BHb3iUF2dVGPmRwmjyLHdCpdZi-LXRrqbEdqIK9uhGZzDmKI0jhA5R8N2x-g5EFqMW-_wncl7XQ] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [8] - [USER] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [9] - [null] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [10] - [null] 2023-08-15T02:09:31.489+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results : Extracted JDBC value [11] - [test] 2023-08-15T02:09:31.490+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.hibernate.orm.results.loading.entity : (EntityResultInitializer) Done materializing entityInstance : com.example.wechall.domain.entity.user.User#30 2023-08-15T02:09:31.490+09:00 DEBUG 21312 --- [nio-8080-exec-1] org.hibernate.orm.results.loading : Calling top-level assembler (0 / 1) : org.hibernate.sql.results.graph.entity.internal.EntityAssembler@48db2025 2023-08-15T02:09:31.491+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.orm.jpa.JpaTransactionManager : Initiating transaction commit 2023-08-15T02:09:31.491+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.orm.jpa.JpaTransactionManager : Committing JPA transaction on EntityManager [SessionImpl(925013769)] 2023-08-15T02:09:31.491+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.h.e.t.internal.TransactionImpl : committing 2023-08-15T02:09:31.491+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.jdbc.datasource.DataSourceUtils : Resetting read-only flag of JDBC Connection [HikariProxyConnection@227483378 wrapping conn1: url=jdbc:h2:~/wechall user=SA] 2023-08-15T02:09:31.491+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.orm.jpa.JpaTransactionManager : Not closing pre-bound JPA EntityManager after transaction 2023-08-15T02:09:31.585+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.w.s.m.m.a.HttpEntityMethodProcessor : Using 'application/octet-stream', given [*/*] and supported [*/*] 2023-08-15T02:09:31.585+09:00 DEBUG 21312 --- [nio-8080-exec-1] c.e.w.c.interceptor.LoggerInterceptor : ==================== END ====================== 2023-08-15T02:09:31.586+09:00 DEBUG 21312 --- [nio-8080-exec-1] c.e.w.c.interceptor.LoggerInterceptor : =============================================== 2023-08-15T02:09:31.586+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.j.s.OpenEntityManagerInViewInterceptor : Closing JPA EntityManager in OpenEntityManagerInViewInterceptor 2023-08-15T02:09:31.586+09:00 DEBUG 21312 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Completed 200 OK

그렌리옹 · Answer

제가 알기로는 transactional 어노테이션 건 함수내 전 기능이 동일한 트랜잭션 관리하에 놓이는게 맞습니다 findbyid 시점과 update 와 다른 트랜잭션을 원하신다면 서비스상에서 함수 분리하셔야 하고 제 생각에는 그냥 지금대로 쓰시는게 올바른 방식으로 보입니다같은 1차 캐시를 공유해야 하니까요

스프링부트 서비스 layer에서 @Transactional 작동 안하는 문제..

1개의 답변

Q&A 목록