chanan / chanan/Play2JavaRabbitMQ
Not using declared queues, instead creating new queue for every call
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi
Nice work done for a get started with Java-Play25x-rabbitmq.
I found 2 issues in the code. Could you explain if there is a reason for maintaining it that way ?
- For every call made, the system creates a default queue and not using the declared rpcqueue and presonRepoQueue.
- While starting the application, the system requires the declared queues to be existing in rabbitmq, else it does not create.
is there something missing in what I'm doing ?
thanx
bw
Contributor guide
No contributing guide indexed for this repository
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 tracing the RabbitMQ connection, queue declaration, and per-call queue creation paths, focusing on rpcqueue and presonRepoQueue. Reproduce startup with those queues absent and inspect the behavior of each call. Done means the intended queue lifecycle is documented or corrected and both reported cases are covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, rabbitmq
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100