Maybe a new system value has affected your dataqueues behavior.
Thinking to delete the dataqueue and create it again maybe help you, specifying MAXLEN parameter for a maximun message length and SIZE parameter for maximun enqueued messages.
Regards.
Last Wiki Answer Submitted: March 14, 2011 6:30 pm by Mariodlg2,790 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
If it is apps, then whatever is supposed to be reading entries off of the queue is not reading them fast enough. Either the rate of adding entries to the queue needs to be slowed or the rate of reading them needs to be quickened. The standard means of speeding up reading from the queue is to start one or more additional readers.
Entries on a data queue are generally expected to be read immediately. A data queue is not intended for long term storage; it is intended as a low-overhead way of passing data elements from one process to another.
You should think in terms of never having more than a few entries on a data queue at one time. By reading the entries quickly, there should never be a time when the queue is filled.
Also, keep in mind that entries on a data queue are not saved when the data queue object is saved. That means that the entries are lost if the data queue must be restored. That’s a strong reason not to think of data queues as permanent storage containers.
You’ll get that message when an attempt is made to add an entry to the data queue when the maximum number of entries are already on the queue.
Is this one of your data queues? Or is this a data queue in a software product?
Tom
if it is apps, then you can ask them to modify the dataq lenght and also how long they want to keep it
If it is apps, then whatever is supposed to be reading entries off of the queue is not reading them fast enough. Either the rate of adding entries to the queue needs to be slowed or the rate of reading them needs to be quickened. The standard means of speeding up reading from the queue is to start one or more additional readers.
Entries on a data queue are generally expected to be read immediately. A data queue is not intended for long term storage; it is intended as a low-overhead way of passing data elements from one process to another.
You should think in terms of never having more than a few entries on a data queue at one time. By reading the entries quickly, there should never be a time when the queue is filled.
Also, keep in mind that entries on a data queue are not saved when the data queue object is saved. That means that the entries are lost if the data queue must be restored. That’s a strong reason not to think of data queues as permanent storage containers.
Tom