Re: Strange issue with a Data Queue -- MIDRANGE-L

Subject: Re: Strange issue with a Data Queue
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Sun, 25 Jan 2015 12:39:41 -0600
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 22-Jan-2015 09:39 -0600, Rich Loeber wrote:

In our extensive experience with data queues, we have found that
they are easily damaged and what you are seeing seems to fit that
situation. <<SNIP>>

Even so, there should be evidence of 'damage' both in the [history and\or VLic] logs; likely something similar for the alluded possible object size\storage [or user profile storage] limit being reached. Thus evidence of the origin may persist, irrespective the failure to keep joblog(s) of the apparently /failed/ Send Data Queue Entry (QSNDDTAQ) API requests.

Note: The *DTAQ object can be journaled to both make the objects more robust and for evidence of messaging activity to\from the Data Queue.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.