IT:Queues/en: Perbedaan revisi
(Replaced content with "==emailouput==") |
|||
| Baris 7: | Baris 7: | ||
==emailouput== | ==emailouput== | ||
| − | ==reportrequest== | + | ==reportrequest== |
| − | |||
==deadletter== | ==deadletter== | ||
This is a special queue for messages which could not be processed. Normally, un-handled messages are placed back on the queue so another server can process them. However, after 20 attempts, if the message has not been successfully processed, there is either a problem with the message format or with the server. In this case the message is placed in the deadletter queue. Messages from the deadletter queue are reported regularly to administrators for debugging purposes. | This is a special queue for messages which could not be processed. Normally, un-handled messages are placed back on the queue so another server can process them. However, after 20 attempts, if the message has not been successfully processed, there is either a problem with the message format or with the server. In this case the message is placed in the deadletter queue. Messages from the deadletter queue are reported regularly to administrators for debugging purposes. | ||
Revisi per 2 September 2014 17.08
Queues
The following queues are used within iSIKHNAS to transfer tasks between different elastic servers.
emailinput
emailouput
reportrequest
deadletter
This is a special queue for messages which could not be processed. Normally, un-handled messages are placed back on the queue so another server can process them. However, after 20 attempts, if the message has not been successfully processed, there is either a problem with the message format or with the server. In this case the message is placed in the deadletter queue. Messages from the deadletter queue are reported regularly to administrators for debugging purposes.