[Memory Leakage] Connection, ResultSet, Statement are not closed

dazzling-sky / COMP4111-project

COMP4111 project - RESTful Web Service for Library Book Management

0 stars 0 forks source link

Open chanhyeok95 opened 4 years ago

chanhyeok95 commented 4 years ago

Bug Kind: Resource Leakage How to reproduce bug: Run any logic that has connection to DB

All the connections to DB should be closed explicitly after usage, as it can potentially lead to memory leakage problem if not closed explicitly.

I have regarded this issue as a bug because TA's regarded this issue as a bug.

comp4111ta commented 4 years ago