Re: EXTERNAL: Reasons for Entry ID increasing
It stopped to increase the ID. Also, I found the code trying to create the request... Added a log to file action with `! and the use of id's is directly related to the code execution. Now, I start debugging. Thanks! Jose Manuel Huerta http://theremedyforit.com/ On Tue, Sep 11, 2012 at 9:23 AM, Jose Manuel Huerta Guillén < arsl...@theremedyforit.com> wrote: > Next-ID-Commit is T. > > Added the Next-ID-Commit F > > > Jose Manuel Huerta > http://theremedyforit.com/ > > > > > On Tue, Sep 11, 2012 at 8:46 AM, Misi Mladoniczky wrote: > >> Hi, >> >> What is the form specific value for the block size? >> >> Do you have Next-ID-Commit set to T? In that case it will not roll back >> the id if it fails. If there is no value present, try adding >> Next-ID-Commit:F. >> >> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) >> >> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. >> Find these products, and many free tools and utilities, at http://rrr.se. >> >> > Sorry, but I forgot to add version. >> > >> > ARS 7.5 patch 7 >> > DB Oracle RAC 11G >> > >> > The Next ID is set to 1. This behavior only happens on one form, the >> rest >> > of the forms are working as expected. After the 155, the next Id >> delivered >> > was 743. >> > >> > I have some escalations that can do a PUSH on this form. I'm suspecting >> > that one of these escalations is trying to do the PUSH every 10 minutes, >> > and gets an error. But the ID is obtained. Because the error is an SQL >> > one, >> > and done after all processing is made and the transaction getting the ID >> > is >> > made. But I still haven't found exactly where... >> > >> > >> > Jose Manuel Huerta >> > http://theremedyforit.com/ >> > >> > >> > >> > >> > On Tue, Sep 11, 2012 at 7:59 AM, Misi Mladoniczky wrote: >> > >> >> Hi, >> >> >> >> I have posted this many times ;-) >> >> >> >> The default settings in 7.6.04 has changed: >> >> >> >> New 7.6.04 default behavior (if lines are not present in ar.cfg): >> >> Next-ID-Commit:T >> >> Next-ID-Block-Size:25 >> >> >> >> Old 7.6.03 and earlier default behavior: >> >> Next-ID-Commit:F >> >> Next-ID-Block-Size:1 >> >> >> >> So to get the old behavior just put F/1 in the ar.cfg/conf file. >> >> >> >> Note that you can set the Next-ID-Block-Size on a per form basis as >> >> well, >> >> so you could have the 25-blocks as default but 1 for a specific form. >> >> >> >> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP >> >> 2011) >> >> >> >> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): >> >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. >> >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy >> >> logs. >> >> Find these products, and many free tools and utilities, at >> >> http://rrr.se. >> >> >> >> > Jose, >> >> > >> >> > What do you have set for Next Request ID Block Size? >> >> > It's on the Configuration tab of the Server Information page. >> >> > Yours looks like it is set to 150 >> >> > >> >> > >> >> > Thank you, >> >> > --- >> >> > John J. Reiser >> >> > Remedy Developer/Administrator >> >> > Senior Software Development Analyst >> >> > Lockheed Martin - MS2 >> >> > The star that burns twice as bright burns half as long. >> >> > Pay close attention and be illuminated by its brilliance. - >> >> paraphrased >> >> by >> >> > me >> >> > >> >> > From: Action Request System discussion list(ARSList) >> >> > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Manuel Huerta Guillén >> >> > Sent: Monday, September 10, 2012 5:04 PM >> >> > To: arslist@ARSLIST.ORG >> >> > Subject: EXTERNAL: Reasons for Entry ID increasing >> >> > >> >> > ** Hi, >> >&g
Re: EXTERNAL: Reasons for Entry ID increasing
Next-ID-Commit is T. Added the Next-ID-Commit F Jose Manuel Huerta http://theremedyforit.com/ On Tue, Sep 11, 2012 at 8:46 AM, Misi Mladoniczky wrote: > Hi, > > What is the form specific value for the block size? > > Do you have Next-ID-Commit set to T? In that case it will not roll back > the id if it fails. If there is no value present, try adding > Next-ID-Commit:F. > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > > Sorry, but I forgot to add version. > > > > ARS 7.5 patch 7 > > DB Oracle RAC 11G > > > > The Next ID is set to 1. This behavior only happens on one form, the rest > > of the forms are working as expected. After the 155, the next Id > delivered > > was 743. > > > > I have some escalations that can do a PUSH on this form. I'm suspecting > > that one of these escalations is trying to do the PUSH every 10 minutes, > > and gets an error. But the ID is obtained. Because the error is an SQL > > one, > > and done after all processing is made and the transaction getting the ID > > is > > made. But I still haven't found exactly where... > > > > > > Jose Manuel Huerta > > http://theremedyforit.com/ > > > > > > > > > > On Tue, Sep 11, 2012 at 7:59 AM, Misi Mladoniczky wrote: > > > >> Hi, > >> > >> I have posted this many times ;-) > >> > >> The default settings in 7.6.04 has changed: > >> > >> New 7.6.04 default behavior (if lines are not present in ar.cfg): > >> Next-ID-Commit:T > >> Next-ID-Block-Size:25 > >> > >> Old 7.6.03 and earlier default behavior: > >> Next-ID-Commit:F > >> Next-ID-Block-Size:1 > >> > >> So to get the old behavior just put F/1 in the ar.cfg/conf file. > >> > >> Note that you can set the Next-ID-Block-Size on a per form basis as > >> well, > >> so you could have the 25-blocks as default but 1 for a specific form. > >> > >> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP > >> 2011) > >> > >> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): > >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. > >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy > >> logs. > >> Find these products, and many free tools and utilities, at > >> http://rrr.se. > >> > >> > Jose, > >> > > >> > What do you have set for Next Request ID Block Size? > >> > It's on the Configuration tab of the Server Information page. > >> > Yours looks like it is set to 150 > >> > > >> > > >> > Thank you, > >> > --- > >> > John J. Reiser > >> > Remedy Developer/Administrator > >> > Senior Software Development Analyst > >> > Lockheed Martin - MS2 > >> > The star that burns twice as bright burns half as long. > >> > Pay close attention and be illuminated by its brilliance. - > >> paraphrased > >> by > >> > me > >> > > >> > From: Action Request System discussion list(ARSList) > >> > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Manuel Huerta Guillén > >> > Sent: Monday, September 10, 2012 5:04 PM > >> > To: arslist@ARSLIST.ORG > >> > Subject: EXTERNAL: Reasons for Entry ID increasing > >> > > >> > ** Hi, > >> > > >> > We just deployed a custom app in production and we see a very strange > >> > behavior. One of the main forms is creating very big spaces in entry > >> ID > >> > numbering. It seems that something is "using" entry id numbers. It is > >> > correlated with time. So if we create two requests very close in time, > >> > they typically have consecutive numbers. But if we wait some hours, > >> the > >> > next number can be hundreds for the previous. > >> > > >> > For instance, from entry EPD0006, the next was EPD0155 > >> > > >> > I'm suspecting that maybe the problem is that I have something that > >> m
Re: EXTERNAL: Reasons for Entry ID increasing
Hi, What is the form specific value for the block size? Do you have Next-ID-Commit set to T? In that case it will not roll back the id if it fails. If there is no value present, try adding Next-ID-Commit:F. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Sorry, but I forgot to add version. > > ARS 7.5 patch 7 > DB Oracle RAC 11G > > The Next ID is set to 1. This behavior only happens on one form, the rest > of the forms are working as expected. After the 155, the next Id delivered > was 743. > > I have some escalations that can do a PUSH on this form. I'm suspecting > that one of these escalations is trying to do the PUSH every 10 minutes, > and gets an error. But the ID is obtained. Because the error is an SQL > one, > and done after all processing is made and the transaction getting the ID > is > made. But I still haven't found exactly where... > > > Jose Manuel Huerta > http://theremedyforit.com/ > > > > > On Tue, Sep 11, 2012 at 7:59 AM, Misi Mladoniczky wrote: > >> Hi, >> >> I have posted this many times ;-) >> >> The default settings in 7.6.04 has changed: >> >> New 7.6.04 default behavior (if lines are not present in ar.cfg): >> Next-ID-Commit:T >> Next-ID-Block-Size:25 >> >> Old 7.6.03 and earlier default behavior: >> Next-ID-Commit:F >> Next-ID-Block-Size:1 >> >> So to get the old behavior just put F/1 in the ar.cfg/conf file. >> >> Note that you can set the Next-ID-Block-Size on a per form basis as >> well, >> so you could have the 25-blocks as default but 1 for a specific form. >> >> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP >> 2011) >> >> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): >> * RRR|License - Not enough Remedy licenses? Save money by optimizing. >> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy >> logs. >> Find these products, and many free tools and utilities, at >> http://rrr.se. >> >> > Jose, >> > >> > What do you have set for Next Request ID Block Size? >> > It's on the Configuration tab of the Server Information page. >> > Yours looks like it is set to 150 >> > >> > >> > Thank you, >> > --- >> > John J. Reiser >> > Remedy Developer/Administrator >> > Senior Software Development Analyst >> > Lockheed Martin - MS2 >> > The star that burns twice as bright burns half as long. >> > Pay close attention and be illuminated by its brilliance. - >> paraphrased >> by >> > me >> > >> > From: Action Request System discussion list(ARSList) >> > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Manuel Huerta Guillén >> > Sent: Monday, September 10, 2012 5:04 PM >> > To: arslist@ARSLIST.ORG >> > Subject: EXTERNAL: Reasons for Entry ID increasing >> > >> > ** Hi, >> > >> > We just deployed a custom app in production and we see a very strange >> > behavior. One of the main forms is creating very big spaces in entry >> ID >> > numbering. It seems that something is "using" entry id numbers. It is >> > correlated with time. So if we create two requests very close in time, >> > they typically have consecutive numbers. But if we wait some hours, >> the >> > next number can be hundreds for the previous. >> > >> > For instance, from entry EPD0006, the next was EPD0155 >> > >> > I'm suspecting that maybe the problem is that I have something that >> makes >> > a PUSH to create a requests that ends into error, so the ID was taken >> but >> > the request was finally not created. I was planning to use a filter to >> a >> > log file with the `! option in the name, to track those errors. But >> don't >> > know. Also the configuration parameter at the ARS server to cache >> entry >> id >> > numbers is set to 1, so no cache is made, and this behavior is not >> seen >> at >> > any other form. >> > >> > Do you know why could this happen? >> > >> > Regards, >> > >> > >> > Jose Manuel Huerta &g
Re: EXTERNAL: Reasons for Entry ID increasing
Sorry, but I forgot to add version. ARS 7.5 patch 7 DB Oracle RAC 11G The Next ID is set to 1. This behavior only happens on one form, the rest of the forms are working as expected. After the 155, the next Id delivered was 743. I have some escalations that can do a PUSH on this form. I'm suspecting that one of these escalations is trying to do the PUSH every 10 minutes, and gets an error. But the ID is obtained. Because the error is an SQL one, and done after all processing is made and the transaction getting the ID is made. But I still haven't found exactly where... Jose Manuel Huerta http://theremedyforit.com/ On Tue, Sep 11, 2012 at 7:59 AM, Misi Mladoniczky wrote: > Hi, > > I have posted this many times ;-) > > The default settings in 7.6.04 has changed: > > New 7.6.04 default behavior (if lines are not present in ar.cfg): > Next-ID-Commit:T > Next-ID-Block-Size:25 > > Old 7.6.03 and earlier default behavior: > Next-ID-Commit:F > Next-ID-Block-Size:1 > > So to get the old behavior just put F/1 in the ar.cfg/conf file. > > Note that you can set the Next-ID-Block-Size on a per form basis as well, > so you could have the 25-blocks as default but 1 for a specific form. > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > > Jose, > > > > What do you have set for Next Request ID Block Size? > > It's on the Configuration tab of the Server Information page. > > Yours looks like it is set to 150 > > > > > > Thank you, > > --- > > John J. Reiser > > Remedy Developer/Administrator > > Senior Software Development Analyst > > Lockheed Martin - MS2 > > The star that burns twice as bright burns half as long. > > Pay close attention and be illuminated by its brilliance. - paraphrased > by > > me > > > > From: Action Request System discussion list(ARSList) > > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Manuel Huerta Guillén > > Sent: Monday, September 10, 2012 5:04 PM > > To: arslist@ARSLIST.ORG > > Subject: EXTERNAL: Reasons for Entry ID increasing > > > > ** Hi, > > > > We just deployed a custom app in production and we see a very strange > > behavior. One of the main forms is creating very big spaces in entry ID > > numbering. It seems that something is "using" entry id numbers. It is > > correlated with time. So if we create two requests very close in time, > > they typically have consecutive numbers. But if we wait some hours, the > > next number can be hundreds for the previous. > > > > For instance, from entry EPD0006, the next was EPD0155 > > > > I'm suspecting that maybe the problem is that I have something that makes > > a PUSH to create a requests that ends into error, so the ID was taken but > > the request was finally not created. I was planning to use a filter to a > > log file with the `! option in the name, to track those errors. But don't > > know. Also the configuration parameter at the ARS server to cache entry > id > > numbers is set to 1, so no cache is made, and this behavior is not seen > at > > any other form. > > > > Do you know why could this happen? > > > > Regards, > > > > > > Jose Manuel Huerta > > http://theremedyforit.com/ > > > > > > _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the > > Answers Are"_ > > > > > ___ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Reasons for Entry ID increasing
Hi, I have posted this many times ;-) The default settings in 7.6.04 has changed: New 7.6.04 default behavior (if lines are not present in ar.cfg): Next-ID-Commit:T Next-ID-Block-Size:25 Old 7.6.03 and earlier default behavior: Next-ID-Commit:F Next-ID-Block-Size:1 So to get the old behavior just put F/1 in the ar.cfg/conf file. Note that you can set the Next-ID-Block-Size on a per form basis as well, so you could have the 25-blocks as default but 1 for a specific form. Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Jose, > > What do you have set for Next Request ID Block Size? > It's on the Configuration tab of the Server Information page. > Yours looks like it is set to 150 > > > Thank you, > --- > John J. Reiser > Remedy Developer/Administrator > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Manuel Huerta Guillén > Sent: Monday, September 10, 2012 5:04 PM > To: arslist@ARSLIST.ORG > Subject: EXTERNAL: Reasons for Entry ID increasing > > ** Hi, > > We just deployed a custom app in production and we see a very strange > behavior. One of the main forms is creating very big spaces in entry ID > numbering. It seems that something is "using" entry id numbers. It is > correlated with time. So if we create two requests very close in time, > they typically have consecutive numbers. But if we wait some hours, the > next number can be hundreds for the previous. > > For instance, from entry EPD0006, the next was EPD0155 > > I'm suspecting that maybe the problem is that I have something that makes > a PUSH to create a requests that ends into error, so the ID was taken but > the request was finally not created. I was planning to use a filter to a > log file with the `! option in the name, to track those errors. But don't > know. Also the configuration parameter at the ARS server to cache entry id > numbers is set to 1, so no cache is made, and this behavior is not seen at > any other form. > > Do you know why could this happen? > > Regards, > > > Jose Manuel Huerta > http://theremedyforit.com/ > > > _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the > Answers Are"_ > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: EXTERNAL: Reasons for Entry ID increasing
Jose, What do you have set for Next Request ID Block Size? It's on the Configuration tab of the Server Information page. Yours looks like it is set to 150 Thank you, --- John J. Reiser Remedy Developer/Administrator Senior Software Development Analyst Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jose Manuel Huerta Guillén Sent: Monday, September 10, 2012 5:04 PM To: arslist@ARSLIST.ORG Subject: EXTERNAL: Reasons for Entry ID increasing ** Hi, We just deployed a custom app in production and we see a very strange behavior. One of the main forms is creating very big spaces in entry ID numbering. It seems that something is "using" entry id numbers. It is correlated with time. So if we create two requests very close in time, they typically have consecutive numbers. But if we wait some hours, the next number can be hundreds for the previous. For instance, from entry EPD0006, the next was EPD0155 I'm suspecting that maybe the problem is that I have something that makes a PUSH to create a requests that ends into error, so the ID was taken but the request was finally not created. I was planning to use a filter to a log file with the `! option in the name, to track those errors. But don't know. Also the configuration parameter at the ARS server to cache entry id numbers is set to 1, so no cache is made, and this behavior is not seen at any other form. Do you know why could this happen? Regards, Jose Manuel Huerta http://theremedyforit.com/ _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Reasons for Entry ID increasing
Hi, We just deployed a custom app in production and we see a very strange behavior. One of the main forms is creating very big spaces in entry ID numbering. It seems that something is "using" entry id numbers. It is correlated with time. So if we create two requests very close in time, they typically have consecutive numbers. But if we wait some hours, the next number can be hundreds for the previous. For instance, from entry EPD0006, the next was EPD0155 I'm suspecting that maybe the problem is that I have something that makes a PUSH to create a requests that ends into error, so the ID was taken but the request was finally not created. I was planning to use a filter to a log file with the `! option in the name, to track those errors. But don't know. Also the configuration parameter at the ARS server to cache entry id numbers is set to 1, so no cache is made, and this behavior is not seen at any other form. Do you know why could this happen? Regards, Jose Manuel Huerta http://theremedyforit.com/ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
