Shawn: The http 500 error is caused by the application crashing. Tomcat will 
write the stack trace to localhost.log and typically to the screen too. If you 
search your log files for "exception", you probably have lots. Our lives, 
debugging SSO issues, is often made tough through log files that are literally 
an ocean of exceptions (usually from the over-engineered cache). 

The Caught Exception problem seems to be a "catch all" piece of Javascript, 
effectively swallowing all the evidence required to fix the core fault in the 
Javascript. It looks like someone added this catch all, and now BMC support is 
flooded with quality issues, but can not reproduce them as the evidence (stack 
trace, stack contents, item of workflow being executed) is lost. 

The poster who deletes the cache on startup provides interesting feedback on 
the Mid Tier cache. I literally don't understand why it exists on disc given 
Mid Tier crawls ITSM, bringing Tomcat to a standstill, for 30minutes after 
Tomcat starts. The idea of a cache is to avoid refetching data! :) I have 
looked at how I can rewrite the caching but the problems go too deep into Mid 
Tier. I put some tracing around it and discovered, in places, Mid Tier is 
loading all the fields on a form and then not using them. I concluded that 
without source code, I couldn't make the cache work efficiently.


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to