- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
ID: java-best-practices/avoid-printstacktrace
Language: Java
Severity: Warning
Category: Best Practices
Use a logging framework instead of printStackTrace()
when handling exceptions. printStackTrace()
can be useful during development for quick debugging, but it is not suitable for production code.
class Foo {
void bar() {
try {
// removed for brevity
} catch (MyException myException) {
myException.printStackTrace();
} catch (Exception e) {
if ("foo" != "bar") {
e.printStackTrace();
}
}
}
}
class Foo {
void bar() {
try {
// removed for brevity
} catch (MyException myException) {
myException.printStackTrace();
} catch (Exception e) {
if ("foo" != "bar") {
e.printStackTrace();
}
}
}
}
import java.util.logging.Logger;
class Foo {
private static final Logger logger = Logger.getLogger(Foo.class.getName());
void bar() {
try {
// Code that may throw an exception
throw new RuntimeException("Something went wrong!");
} catch (Exception e) {
// Log the exception using the Java logger
logger.severe("An error occurred:");
logger.severe(e.toString());
if ("foo" != "bar") {
// Log the exception again if needed
logger.severe("An error occurred in an additional context:");
logger.severe(e.toString());
}
}
}
}
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products