HI All,
I have a situation that occasionally occurs during peak submit periods. On two
incidents the Incident ID and entry id are in sequence but the Submit dates are
not in sequence. I have a VIP to two mid-tiers which are load balanced to 2 AR
Servers in a server group. Both AR servers use
Mark,
Are you in a Server Group? If so, you will find that each server has its
own cache of next ID's.
On Wed, Jul 3, 2013 at 10:11 AM, Brittain, Mark mbritt...@navisite.comwrote:
**
HI All,
** **
I have a situation that occasionally occurs during peak submit periods. On
two
Hennigan
Remedy Developer
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Brittain, Mark
Sent: Wednesday, July 03, 2013 12:12 PM
To: arslist@ARSLIST.ORG
Subject: Submit Date out of Sequence
**
HI All,
I have a situation that occasionally occurs during
Hi Mark,
There is a configuration for Next Request ID Block Size on the Server
Information form / Configuration tab. Basically, what happens is each
thread gets its own block of IDs to use.
There's also the Next-ID-Commit setting, which is a T/F value in
ar.conf/ar.cfg which will make sure that
And if your system is set to pre-fetch more than one Entry Id at a time,
this will happen. Which is one of the reasons that most Remedy systems
shouldn't have it set above 1.
Rick
On Jul 3, 2013 9:36 AM, Longwing, Lj llongw...@usgs.gov wrote:
**
Mark,
Are you in a Server Group? If so, you
If you look in the server information form, there's a setting for next ID block
size. It's typically set to 100. When each server in your server group boots
up, it caches 100 IDs and updates the nextId for each form in the arschema
table. This is to prevent an update and select statement to the
6 matches
Mail list logo
