KB-1104 How to capture SQL statements using Hibernate trace logs

Devon Lee — Tue, 07 Nov 2023 20:32:50 GMT

Current Revision posted to Appian Knowledge Base by Devon Lee on 11/7/2023 8:32:50 PM

In certain troubleshooting scenarios, it may be necessary to retrieve the details of database queries that are being performed by Appian. This article details how to enable Hibernate Tracing, which results in the queries made by Appian being logged to the application server logs.

To enable Hibernate Tracing:

Open the appian_log4j.properties file. For Appian 18.3 and later, this file can be found in <APPIAN_HOME>/deployment/web.war/WEB-INF/resources. For Appian 18.2 and earlier, this file can be found in <APPIAN_HOME>/ear/suite.ear/resources.

Find and uncomment the "Output SQL Statements" and "Output param values within SQL statements" sections:

# Output SQL statements
log4j.logger.org.hibernate.SQL=DEBUG
# Output param values within SQL statements
log4j.logger.org.hibernate.type=TRACE

Set "Output SQL statements" to DEBUG if it is not already set.
Set "Output param values within SQL statements" to TRACE if it is not already set.

Once Hibernate Trace logging is no longer required, return to the appian_log4j.properties file, and update the above lines to the following:

# Output SQL statements
log4j.logger.org.hibernate.SQL=ERROR
# Output param values within SQL statements
log4j.logger.org.hibernate.type=ERROR

Save the file and check the application server log to verify that the DEBUG and TRACE log entries are no longer being recorded.
After verifying that DEBUG and TRACE entries are no longer being logged via the above step, it is safe to comment those lines out if desired.

Some things to note after following these steps:

No application server restart is necessary as these changes are hot-deployed.
The DEBUG and TRACE entries should show up in the application server logs.
The DEBUG setting mentioned above will log the queries, whereas the TRACE setting mentioned above will log the values for the queries.
It is NOT recommended to enable Hibernate Trace logging unless requested by Appian Support to troubleshoot a specific issue because these settings may negatively affect performance.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: logging, administration, database, application server, how-to

KB-1104 How to capture SQL statements using Hibernate trace logs

Devon Lee — Tue, 07 Nov 2023 20:32:47 GMT

Revision 4 posted to Appian Knowledge Base by Devon Lee on 11/7/2023 8:32:47 PM

To enable Hibernate Tracing:

Open the appian_log4j.properties file. For Appian 18.3 and later, this file can be found in <APPIAN_HOME>/deployment/web.war/WEB-INF/resources. For Appian 18.2 and earlier, this file can be found in <APPIAN_HOME>/ear/suite.ear/resources.

Find and uncomment the "Output SQL Statements" and "Output param values within SQL statements" sections:

# Output SQL statements
log4j.logger.org.hibernate.SQL=DEBUG
# Output param values within SQL statements
log4j.logger.org.hibernate.type=TRACE

Set "Output SQL statements" to DEBUG if it is not already set.
Set "Output param values within SQL statements" to TRACE if it is not already set.

Once Hibernate Trace logging is no longer required, return to the appian_log4j.properties file, and update the above lines to the following:

# Output SQL statements
log4j.logger.org.hibernate.SQL=ERROR
# Output param values within SQL statements
log4j.logger.org.hibernate.type=ERROR

Save the file and check the application server log to verify that the DEBUG and TRACE log entries are no longer being recorded.
After verifying that DEBUG and TRACE entries are no longer being logged via the above step, it is safe to comment those lines out if desired.

Some things to note after following these steps:

No application server restart is necessary as these changes are hot-deployed.
The DEBUG and TRACE entries should show up in the application server logs.
The DEBUG setting mentioned above will log the queries, whereas the TRACE setting mentioned above will log the values for the queries.
It is NOT recommended to enable Hibernate Trace logging unless requested by Appian Support to troubleshoot a specific issue because these settings may negatively affect performance.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: logging, administration, database, application server, how-to

KB-1104 How to capture SQL statements using Hibernate trace logs

Parmida Borhani — Wed, 26 Jun 2019 06:19:21 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 6/26/2019 6:19:21 AM

To enable Hibernate Tracing:

Open the appian_log4j.properties file. For Appian 18.3 and later, this file can be found in <APPIAN_HOME>/deployment/web.war/WEB-INF/resources. For Appian 18.2 and earlier, this file can be found in <APPIAN_HOME>/ear/suite.ear/resources.

Find and uncomment the "Output SQL Statements" and "Output param values within SQL statements" sections:

# Output SQL statements
log4j.logger.org.hibernate.SQL=DEBUG
# Output param values within SQL statements
log4j.logger.org.hibernate.type=TRACE

Set "Output SQL statements" to DEBUG if it is not already set.
Set "Output param values within SQL statements" to TRACE if it is not already set.

Once Hibernate Trace logging is no longer required, return to the appian_log4j.properties file, and update the above lines to the following:

# Output SQL statements
log4j.logger.org.hibernate.SQL=ERROR
# Output param values within SQL statements
log4j.logger.org.hibernate.type=ERROR

Save the file and check the application server log to verify that the DEBUG and TRACE log entries are no longer being recorded.
After verifying that DEBUG and TRACE entries are no longer being logged via the above step, it is safe to comment those lines out if desired.

Some things to note after following these steps:

No application server restart is necessary as these changes are hot-deployed.
The DEBUG and TRACE entries should show up in the application server logs.
The DEBUG setting mentioned above will log the queries, whereas the TRACE setting mentioned above will log the values for the queries.
It is NOT recommended to enable Hibernate Trace logging unless requested by Appian Support to troubleshoot a specific issue because these settings may negatively affect performance.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: logging, administration, database, application server, how-to

KB-1104 How to capture SQL statements using Hibernate trace logs

Nick Vigilante — Wed, 22 Feb 2017 22:43:19 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 10:43:19 PM

To enable Hibernate Tracing:

Navigate to <APPIAN_HOME>/ear/suite.ear/resources and open the appian_log4j.properties file.

Find and uncomment the "Output SQL Statements" and "Output param values within SQL statements" sections:

# Output SQL statements
log4j.logger.org.hibernate.SQL=DEBUG
# Output param values within SQL statements
log4j.logger.org.hibernate.type=TRACE

Set "Output SQL statements" to DEBUG if it is not already set.
Set "Output param values within SQL statements" to TRACE if it is not already set.

Once Hibernate Trace logging is no longer required, return to the appian_log4j.properties file, and update the above lines to the following:

# Output SQL statements
log4j.logger.org.hibernate.SQL=ERROR
# Output param values within SQL statements
log4j.logger.org.hibernate.type=ERROR

Save the file and check the JBoss or WebLogic server log to verify that the DEBUG and TRACE log entries are no longer being recorded.
After verifying that DEBUG and TRACE entries are no longer being logged via the above step, it is safe to comment those lines out if desired.

Some things to note after following these steps:

No application server restart is necessary as these changes are hot-deployed.
The DEBUG and TRACE entries should show up in the JBoss or WebLogic server logs.
The DEBUG setting mentioned above will log the queries, whereas the TRACE setting mentioned above will log the values for the queries.
It is NOT recommended to enable Hibernate Trace logging unless requested by Appian Support to troubleshoot a specific issue because these settings may negatively affect performance.

Affected Versions

This article applies to all on-premise installations of Appian.

Last Reviewed: May 2016

Tags: logging, database, application server, how-to

KB-1104 How to capture SQL statements using Hibernate trace logs

Nick Vigilante — Wed, 22 Feb 2017 17:45:10 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 5:45:10 PM

To enable Hibernate Tracing:

Navigate to <APPIAN_HOME>/ear/suite.ear/resources and open the appian_log4j.properties file.

Find and uncomment the "Output SQL Statements" and "Output param values within SQL statements" sections:

# Output SQL statements
log4j.logger.org.hibernate.SQL=DEBUG
# Output param values within SQL statements
log4j.logger.org.hibernate.type=TRACE

Set "Output SQL statements" to DEBUG if it is not already set.
Set "Output param values within SQL statements" to TRACE if it is not already set.

Once Hibernate Trace logging is no longer required, return to the appian_log4j.properties file, and update the above lines to the following:

# Output SQL statements
log4j.logger.org.hibernate.SQL=ERROR
# Output param values within SQL statements
log4j.logger.org.hibernate.type=ERROR

Save the file and check the JBoss or WebLogic server log to verify that the DEBUG and TRACE log entries are no longer being recorded.
After verifying that DEBUG and TRACE entries are no longer being logged via the above step, it is safe to comment those lines out if desired.

Some things to note after following these steps:

No application server restart is necessary as these changes are hot-deployed.
The DEBUG and TRACE entries should show up in the JBoss or WebLogic server logs.
The DEBUG setting mentioned above will log the queries, whereas the TRACE setting mentioned above will log the values for the queries.
It is NOT recommended to enable Hibernate Trace logging unless requested by Appian Support to troubleshoot a specific issue because these settings may negatively affect performance.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2017

Tags: logging, database, application server, how-to