That all makes sense....except I am 100% sure nothing changed since April on the forms.
The only difference I know if is we turned off automatic re-caching 2 days ago in preparation for some training going on and turned on cache persistence...which shouldn't matter since we then flushed the cache. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, June 10, 2008 10:37 AM To: [email protected] Subject: Re: Caught Exception Error (UNCLASSIFIED) My research has shown that this is typically caused by a difference between the js and the actual object definition when changes are made to an object via the admin tool. To elaborate on what I mean: When you view a form in the mid-tier, a series of js files are created on the server side. These are retrieved by the client (browser) and cached. When a change is made to the form in the admin tool, the js is rebuilt the next time the page is viewed. Because the client cached the js, it attempts various dom maneuvering/manipulation of the page rendered by the servlet container; since the page no longer matches what the js is trying to work against, an exception is thrown when some boundary is over stepped. That is why clearing the cache resolves the issue. That is why the problem most typically occurs when a form is changed (e.g., adding/removing table field columns, results list columns, adding/removing fields, etc.). Axton Grams On Tue, Jun 10, 2008 at 10:30 AM, FRANK, GORDON CTR DISA JSSC <[EMAIL PROTECTED]> wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > The fix for this is to clear cache in both the Mid-Tier Config.jsp > and/or your browser cache. This usually does the job. > > You may also have to logout of the Mid-Tier or terminate your userid > through Server Information > > Gordon M. Frank > Remedy Skilled Professional - 7.x > ITIL V3 Foundation Certified > DISA\Verizon FNS > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow > Sent: Tuesday, June 10, 2008 10:22 AM > To: [email protected] > Subject: Caught Exception Error > > ** > In IM 7.03 using the web and going to... > > Application Admin > Custom Config > Foundation > People > People > > I do a search by user ID and get the following error: > > Caught exception :'t.LoadResultsList' is null or not an object > > This is our QA system. It is IDENTICAL to our DEV system and the DEV > system does not throw this error. All of the AR Server and Mid-tier > config settings are the same. I checked previous ARS list posts about > "Caught Exception" errors and none of them applied to this (checked > duplicate fields, results list, etc etc). > > In fact, Migrator says our two copies of CTM:People on the servers are > the same as well. > > Vital stats of the system > AR Server 7.1 patch 001 on Solaris > IM 7.03 > AR Mid-tier 7.1 patch 001 on Solaris (separate box) with IBM HTTP > Server > + Websphere. > > William Rentfrow, Principal Consultant [EMAIL PROTECTED] C > 701-306-6157 O 952-432-0227 > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > Classification: UNCLASSIFIED > Caveats: NONE > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
