Joe, Or it might be an internal Mid-tier problem that goes something like... " Oh.. I need to go fetch/cache that form... so I have nothing to show you right now.. So.. User you go away and when you come back then I will be ready for you." (thus give an error once and start the cache process for that form)
A strange thing about the "dump" cache tool is that it does not trigger a recache (prefetch, or otherwise) operation. I would actually expect that the function should mark all of the cache as "old" and then force a recache of all items already in the cache. However it appears to only "dump and stop". Then the Mid-Tier waits for the next user to "pay the price" for the lack of a cache. LJ, ( Just a thought. ) There was also a perl script that was used with the v6.3 Mid-Tier to "login and force the server to cache objects". (Basically just simulating a user activity of opening the form.) Maybe if your development process incorporated such a step you could stop "dumping" the cache all together? -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 10/16/07, Joe D'Souza <[EMAIL PROTECTED]> wrote: > ** > > In addition of checking out the bug that Michael pointed out, take a SQL log > at the time the error occurs to verify what the system API's are trying to > access at the time of the error. It might reveal something about your error. > > > Joe D'Souza <snip> > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] Behalf Of LJ LongWing (Head) > Sent: Tuesday, October 16, 2007 4:17 PM > To: arslist@ARSLIST.ORG > Subject: 353 Error > > > ARS 7.1 > Mid-Tier 7.1 > New Atlanta ServletExec 5.0.0.13 > Java 1.5.0_11 > Windows 2003 > > We are working in a Test environment and every time we drop code from Dev to > Test we flush the web cache to ensure that the latest code is available to > the testers. We use the Application list on the left of the home page with > entry points heavily on a home grown app. Sometimes, some of the users will > click on an entry point and get a 353 error. Excerpt from Error Message > Guide > > 353 Error > You have no access to form. > You are not allowed to access the specified form. Form permissions do not > allow you to get the definition of the form or of its fields or to access > the data it contains. > Contact your AR System administrator if you need access to the form. > > The funny thing is if they didn't have access to the form...they wouldn't > see the entry point. Even stranger, if they try again immediately after it > works, and continues to work until we flush the cache again. I'm thinking > it's a bug in Mid-Tier 7.1...but can't be sure. Anyone else seen this > problem? Oh...and it only manifests itself in Mid-Tier of course...so no > client interaction with this app. > > LJ LongWing > RAC 7.x Certified _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
