Bug #9964
Updated by Chambon Bernard almost 10 years ago
No that's false
* Caution a queue name (JT819300) could have several queue_id (133, 114)
* Queues are activate by Activator in 'process' method
by iteration over queuesMap
<pre>
.getWaitingQueues(resource.getMediaType());
// getWaitingQueues will retrieve waiting queue from QueuesController.queuesMap
while (waitingQueues.size() > 0)) {
Queue bestQueue = QueuesController.getInstance().getBestQueue(resource, waitingQueues);
</pre>
* For an activated queue name (JT819300), in memory , (I mean in queuesMap) you will have activated queue_id (e.g. 113) and created queue_id (e.g. 114),
this may be surprising !
(this will be done by Activator.activate(bestQueue);)
So in short term , in memory queuesMap (key = JT819300) can be activated, but in DB, queuue_id (113, 114) related to that queue name can be
* At first time I didn't understand why 114 was not all activated.
It will become activated (Thank you very much for code clarity !!!)
* One more thing ...
queuesMap if fiiled by Dispatcher (for sure), when calling addFilePositionOnTape() from submitRequest() (see QueuesController.create())
But if Dispatcher fail for any reason, queuesMap it will never be updated
the best queue !
*Annoying queue name and obviously fille never get stagged !
But why Dispatcher could get blocked ?
queue id are not in a bijection !!!!!*