Page Comparison

Enable logging in QMetry

Navigate
to Setting
to Setting ->System ->
Logging and Profiling tabEnable SQL
Logging and Profiling tab
Enable SQL Loggings for SQL log & SQL dump logs
Scroll the same page below to go
to
to the Default Loggers
section click on Configure link
section click on Configure link
Enter Package name
as “com
as “com.atlassian.
qtm” and
qtm” and Logging level as
“Trace”
“Debug”. Click
on Add
on Add.
In Default Loggers search
In Default Loggers search for the
following Package Name and
following Package Name and click on
“Trace”
“Trace” for the below 3 packages:
- net.java.ao.sql
- net.java.ao.schema.SchemaGenerator
- net.java.ao
Then, go to QMetry → Configuration → Advance Setting: Logging. Set to "Enable"
Once these settings are changed, reproduce the issue on your JIRA instance, so that traces are logged.

Alternatively, you can opt for the below option:

Go to the directory where you have installed JIRA on your server. Fetch the JIRA logs &
share atlassian
share atlassian-jira.
log and Catalina log files
log and Catalina log files with QMetry Support.
For UNIX server: If the directory name is JIRA. You can access logs at JIRA/logs/catalina.out and JIRA/home/log/atlassian-jira.log. In case you do not find the files, trigger the below commands in the UNIX terminal which would fetch the list of logs files path.
- find / -name "atlassian-jira.log" 2>/dev/null
- find / -name "catalina.out" 2>/dev/null
For Windows server : You can access logs from C:\Program Files\Atlassian\JIRA\logs\catalina<Date>.log and C:\Program Files\Atlassian\Application Data\JIRA\log\atlassian-jira.log

Once the logs are provided and the issue is resolved, go
the Default Loggers search
the Default Loggers search for the following package and click on
“Debug”
“Debug” for all three of them.
- net.java.ao.sql
- net.java.ao.schema.SchemaGenerator
- net.java.ao
Go to QMetry → Configuration → Advance Setting : Logging. Set to "Disable". NOTE: The Enabled setting generates more verbose logging. If this is not reverted to "Disabled", it can affect performance and quickly fill up JIRA server logs directory.