Logging

There are several levels of logging that can be performed that will help system troubleshooting. By default, all logging levels are set to Info and will reset to the default upon restarting the server. To permanently change the logging level edit file WEB-INF/log4j.properties.

adminLogging

Click on the Edit link to changes the logging level from the default setting of Info.

adminLoggingSetting

Profiling

What log file is profiling information captured in?

Once enabled, the profiler will log additional content for every log entry in the contour.log.

What information does profiling capture?

Profiling is indicated in the log file as the [jama.Profiler] package. The profiler prints out the following information:

•	The user who submitted the call.

•	The organization the user belongs to.

•	The java thread id of the call.

•	A stack trace of the call that includes processing time and memory usage of each trace.

Notes

Enabling the profiler logging strongly enhances the logging in Contour but may require additional resources to generate this content. For best performance, use the profiler for investigative purposes.

An example log entry:

2011-04-28 09:37:19,865 INFO [org.directwebremoting.impl.DefaultRemoter] - Exec: projectSvc.getExtTreeNodeForProject()

2011-04-28 09:37:19,869 INFO [jama.Profiler] - user:admin org:2 thread:96 start:2011-04-28 09:37:19,866

[3ms] [+88K/-88K 837755K/254041K]- com.jamasoftware.contour.dwr.impl.DwrProjectServiceImpl.getExtTreeNodeForProject

[3ms] [+88K/-88K 837755K/254041K]- com.jamasoftware.contour.service.impl.ProjectServiceImpl.getExtTreeNodeForProject

[2ms] [+88K/-88K 837755K/254041K]- com.jamasoftware.contour.service.impl.DocumentTypeServiceImpl.getAvailableDocumentTypesForProject

Access Log

What log file is profiling information captured in?

contour.log

What information does the access log provide?

The access log captures information of all requests users makes in Contour, whether it is logging in or clicking on an item. Entries in the log file are noted by the [jama.AccessLog] package:

•	Date of the request.

•	Server processing time to handle the request.

•	The user who submitted the request.

•	The organization id of the user who submitted the request.

•	The user session id of the user whom made the request.

•	The server address the request was made to.

An example log entry:

2011-04-28 10:23:40,970 INFO [jama.AccessLog] - [26 ms] admin 2 0E68C37F0B218402D81DEC82D394A63D 91 http://localhost:8080/contour/logout.req ::1

Thread Dump

What log file is profiling information captured in?	contour-threaddump.log
What information does the access log provide?	The thread dump takes a one time dump of the current running java threads being executed. This information is useful for identifying long running processes. If Contour seems to hang, run a thread dump and send the log file to support@jamasoftware.com