OpenBankProject / OpenBankProject/OBP-API
Port once set, seems to always run unless process is killed explicitly
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
On running the App, if an exception occurs, then the port should be closed i.e the process should be killed. Presently, the process happens to keep running on that port and it throws "port in use" error if run again. We have to explicitly kill the process and then proceed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the application exception and checking which process continues to own the port afterward; the issue does not name a file, test, or entry point. Trace the application shutdown and port lifecycle, then verify that an exception releases the port so the application can be run again without manually killing the process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100