I got a response from BMC on my similar issue to upgrade to 7.1.0 patch 2 for the Mid Tier. I don't know if it would resolve everyone's issues, but it may be worth a try.
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cordova, Fred Sent: Friday, April 25, 2008 4:59 PM To: [email protected] Subject: Caught exception errors - our solution ** New thread as I couldn't get the reply to work from the web. I have seen a couple of different caught exception issues with both Servlet Exec and now with Tomcat. The normal one that clears with a user cache flush, seems to happen if users access the mid-tier before the pre-fetch cache finishes building. The other issue we had after the upgrade to 7.1 patch 1 was more persistent. It only affected some users and stayed with them after clearing their cache, even followed to other workstations. We found an inconsistency in the ar system user preferences form. The sort field had reference numbers that were out of range of the current numbers on the form. Not sure how that happened, but it was after 7.1 patch 1. Clearing the sort field in the affected users preferences or having the user reset their results list preferences cleared the issue. Fred Cordova __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
