Logging

  Administration > System administration > System >

Logging

Previous pageNext page Print this topic! Mail us feedback on this topic!

This feature requires user to be logged in as System Administrator.

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 the core Jama application. To permanently change the logging level edit file /data/config/log4j.properties.

The log configuration for Elasticsearch and search service can also be found in /data/config

adminLogging

 

Select Edit to open a pop-up and change 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 Jama 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.Jama.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 Jama, whether it is logging in or selecting an item. It will also store locked out users. 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:

 

2014-08-29 16:24:59,370 INFO http-bio-8080-exec-17 [jama.AccessLog] - [3 ms] PRBDIJN9 1 - 083BBE5B1E8C481033DA7AFBBEF023A5 160 http://localhost:8080/contour/

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 Jama seems to hang, run a thread dump and send the log file to support@jamasoftware.com