Unit 3 - Lesson 7 - Troubleshooting Flashcards
Describe client-side tracing
- Can trace all facade invocations from web tier
When enabled, all in/out from all server calls will be written to standard out. - Negatively affects performance and generates a lot of logging information so it should not be used in a production environment
Every time JSP is requested - you will see that request listed.
How to enable client-side tracing
- Add or enable TraceOn=true in CDEJResources.properties in one of the component folders or webclient/JavaSource/curam/omega3/i18n/CDEJResources.properties
- build client and refresh Eclipse
Describe server tracing
Set of Dynamic properties are available to set tracing levels.
They control what diagnostic information is logged.
Trace settings are made in Application.prx, includes:
curam.trace
curam.trace.servercalls - Server methods invocations by remote clients.
curam.trace.methods - All BPO and Facade method invocations.
curam.trace.method_args - dump arguments to BPO and facade method invocations, including argument type. Only works when curam.trace.method is true or curam.trace at least trace_verbose.
curam.trace.sql - Dump results of SQL select statements.
Which file controls server trace settings?
Application.prx
List and describe values of curam.trace
Tracing is off by default.
trace_on
trace_verbose
trace_ultra_verbose
How to enable and activate server tracing
build insertproperties
or build database followed by startserver to activate any changes to tracing.
Administration Suite can be used to control these properties and avoid db rebuild, stop and restart of server.
Describe basic troubleshooting steps
Check the StartServer console * Is there an exception? * If so, start with the first exception Check Tomcat console Check page for errors * In the browser, right click the page contents to see full URL and any error Turn on server tracing Turn on client tracing Use the IDE debugger