chanan / chanan/Play2JavaRabbitMQ
Not using declared queues, instead creating new queue for every call
- Lingua principale
- Java
- Stelle
- 5
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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 ?
1. For every call made, the system creates a default queue and not using the declared rpcqueue and presonRepoQueue.
2. 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
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, rabbitmq
- Ambito
- backend, distributed-systems
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100