MATE 카풀 (spring boot + queryDSL + JPA + EC2 + RDS)
기존 jpa repositroy에 QueryDSL repository 추가하려면 주의점이 필요하다. interface는 Custom+{EntityName}+Repository 구현한 class 는 Custom+{EntityName}+RepositoryImpl 로 해야 스프링에서 인식한다. 나중에 작성시 유의!
scp -i ~/Documents/aws/shinhanMJ.pem mate.jar ubuntu@3.34.90.140:/home/ubuntu
에러 처리 실패시 기본 서블릿 처리까지 간다. 즉 WAS 까지 가버린다는것. 그중 api 에러 처리에는 ExceptionHandler가 가장 적합함. 커스텀을 적용할수도 있고
File과 Dto를 같이 받기 위해서는 @RequestPart라는 어노테이션이 필요합니다!!
도커에 젠킨스 띄우고 ec2에 스프링부트 올리게 구축하자 12/6에 할일~
test server 13.209.43.209 jenkins sever 43.201.38.135 url 43.201.38.135:9000
http://13.209.43.209:8080/auth/signup
Error code 수정 Validation Handler에서 다 잡아버려서 중복 체크 에러가 처리되지 않음. 이를 분리해서 service에서 중복 체크하게 수정했음. 오류 코드 또한 수정했다. RFC 7231을 보면 중복값의 경우 Conflict 409로 보낸다고 정의됨.
The request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request. The server SHOULD generate a payload that includes enough information for a user to recognize the source of the conflict. -RFC 7231
scp -i ${user.pem} ${fileName} ec2-username@public-ip:${path}
PUT
- PUT can be 201 (if you created the element because that is your behaviour)
- 404 If you don't want to create elements via PUT.
- 400 Bad Request (Malformed syntax or a bad query more common than in case of DELETE).
- 401 Unauthorized
- 403 Forbidden: Authentication failure or invalid Application ID.
- 405 Not Allowed. Sure.
- 409 Resource Conflict can be possible in complex systems, as in DELETE.
- 422 Unprocessable entity It helps to distinguish between a "Bad request" (e.g. malformed XML/JSON) and invalid field values
- And 501, 502 in case of errors.
오늘 프론트 담당자 분으로부터 4MB 이미지 제출시 Broken Pipe 에러가 난다고 전해들었다. 로그를 보니 Maximum size를 넘어서 생긴 오류였다.
2022-12-27 13:53:20.373 DEBUG 121798 --- [nio-8080-exec-6] o.s.web.servlet.DispatcherServlet : POST "/auth/signup", parameters={multipart}
2022-12-27 13:53:20.551 DEBUG 121798 --- [nio-8080-exec-6] .m.m.a.ExceptionHandlerExceptionResolver : Using @ExceptionHandler com.example.eunboard.shared.exception.CommonException#exception(Exception)
2022-12-27 13:53:20.551 INFO 121798 --- [nio-8080-exec-6] c.e.e.shared.exception.CommonException : ! 특정 예외 발생 !
2022-12-27 13:53:20.551 INFO 121798 --- [nio-8080-exec-6] c.e.e.shared.exception.CommonException : org.springframework.web.multipart.MaxUploadSizeExceededException
2022-12-27 13:53:20.551 INFO 121798 --- [nio-8080-exec-6] c.e.e.shared.exception.CommonException : !!!!!! 예외 발생 !!!!!!!!
2022-12-27 13:53:20.551 INFO 121798 --- [nio-8080-exec-6] c.e.e.shared.exception.CommonException : Maximum upload size exceeded; nested exception is java.lang.IllegalStateException: org.apache.tomcat.util.http.fileupload.impl.FileSizeLimitExceededException: The field image exceeds its maximum permitted size of 1048576 bytes.
2022-12-27 13:53:20.552 DEBUG 121798 --- [nio-8080-exec-6] o.s.w.s.m.m.a.HttpEntityMethodProcessor : Using 'text/plain', given [*/*] and supported [text/plain, */*, text/plain, */*, application/json, application/*+json, application/json, application/*+json]
2022-12-27 13:53:20.552 DEBUG 121798 --- [nio-8080-exec-6] o.s.w.s.m.m.a.HttpEntityMethodProcessor : Writing [""]
2022-12-27 13:53:20.558 DEBUG 121798 --- [nio-8080-exec-6] .m.m.a.ExceptionHandlerExceptionResolver : Resolved [org.springframework.web.multipart.MaxUploadSizeExceededException: Maximum upload size exceeded; nested exception is java.lang.IllegalStateException: org.apache.tomcat.util.http.fileupload.impl.FileSizeLimitExceededException: The field image exceeds its maximum permitted size of 1048576 bytes.]
2022-12-27 13:53:20.559 DEBUG 121798 --- [nio-8080-exec-6] o.s.web.servlet.DispatcherServlet : Completed 500 INTERNAL_SERVER_ERROR기존에 max size를 지정했지만 MULTIPART_FORM_DATA_VALUE 으로 받기 때문에 multipart용으로 따로 설정이 필요했다.
spring.servlet.multipart.maxFileSize=10MB
spring.servlet.multipart.maxRequestSize=10MB을 설정에 추가해줬다. 추가 후 테스트한 결과 정상 처리 됨.