KB-1825 Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Fri, 28 Dec 2018 15:42:44 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 3:42:44 PM

Symptoms

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.
The environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42.

Action

Ensure Search Server Is Running without Issues

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors or warnings, follow the Action section of KB-1082 to clear the search server indices and restart the search server.

If Search Server Is Running without Issues...

Ensure that the web server is using the correct connector version. Please see the following details for Apache and IIS:

Apache

If the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.
If the environment is already using Apache 2.4 or later, but the mod_jk version is earlier than 1.2.42, install the latest version of the mod_jk connector and restart Apache.

IIS

If the environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42, upgrade to the most recent version of the isapi_redirect DLL.
Restart IIS.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector. There is no known workaround for IIS at this time.

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Note: This workaround mimics the fix that is implicitly included in the mod_jk version 1.2.41. This workaround should not be a permanent solution, and the recommended course of action is to upgrade both Apache and the mod_jk to the most recent version (and remove this workaround from the httpd.conf file). Leaving this workaround as a long-term solution introduces potential risks if Apache were to change the behavior in that area of the connector in the future. This could expose the environment to problems on subsequent Tomcat versions that are distributed as part of Appian releases.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: IIS, apache, web server, search server, infrastructure

KB-1825 Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Fri, 28 Dec 2018 20:31:20 GMT

Revision 26 posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 8:31:20 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.
The environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42.

Action

Ensure Search Server Is Running without Issues

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors or warnings, follow the Action section of KB-1082 to clear the search server indices and restart the search server.

If Search Server Is Running without Issues...

Ensure that the web server is using the correct connector version. Please see the following details for Apache and IIS:

Apache

If the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.
If the environment is already using Apache 2.4 or later, but the mod_jk version is earlier than 1.2.42, install the latest version of the mod_jk connector and restart Apache.

IIS

If the environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42, upgrade to the most recent version of the isapi_redirect DLL.
Restart IIS.

Workaround

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: IIS, apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 26 Dec 2018 12:50:52 GMT

Revision 25 posted to Appian Knowledge Base by Jordan Horwat on 12/26/2018 12:50:52 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.
The environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42.

Action

Ensure Search Server Is Running without Issues

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors or warnings, follow the Action section of KB-1082 to clear the search server indices and restart the search server.

If Search Server Is Running without Issues...

Ensure that the web server is using the correct connector version. Please see the following details for Apache and IIS:

Apache

If the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.
If the environment is already using Apache 2.4 or later, but the mod_jk version is earlier than 1.2.42, install the latest version of the mod_jk connector and restart Apache.

IIS

If the environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42, upgrade to the most recent version of the isapi_redirect DLL.
Restart IIS.

Workaround

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: IIS, apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 26 Dec 2018 12:50:02 GMT

Revision 24 posted to Appian Knowledge Base by Jordan Horwat on 12/26/2018 12:50:02 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.
The environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42.

Action

Ensure Search Server Is Running without Issues

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors or warnings, follow the Action section of KB-1082 to clear the search server indices and restart the search server.

If Search Server Is Running without Issues...

Ensure that the web server is using the correct connector version. Please see the following details for Apache and IIS:

Apache

If the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.
If the environment is already using Apache 2.4 or later, but the mod_jk version is earlier than 1.2.42, install the latest version of the mod_jk connector and restart Apache.

IIS

If the environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42, upgrade to the most recent version of the isapi_redirect DLL.
Restart IIS.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector. There is no known workaround for IIS.

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: IIS, apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 26 Dec 2018 12:45:04 GMT

Revision 23 posted to Appian Knowledge Base by Jordan Horwat on 12/26/2018 12:45:04 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.
The environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42.

Action

Ensure Search Server Is Running without Issues

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors or warnings, follow the Action section of KB-1082 to clear the search server indices and restart the search server.

If Search Server Is Running without Issues...

Ensure that the web server is using the correct connector version. Please see the following details for Apache and IIS:

Apache

If the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

IIS

If the environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42, upgrade to the most recent version of the isapi_redirect DLL.
Restart IIS.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector. There is no known workaround for IIS.

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 26 Dec 2018 12:36:39 GMT

Revision 22 posted to Appian Knowledge Base by Jordan Horwat on 12/26/2018 12:36:39 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.
The environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42.

Action

Ensure Search Server Is Running without Issues

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors or warnings, follow the Action section of KB-1082 to clear the search server indices and restart the search server.

If Search Server Is Running Without Issues...

Ensure that the web server is using the correct connector version. Please see the following details for Apache and IIS:

Apache

If the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

IIS

If the environment is using a version of the IIS isapi_redirect DLL that is earlier than 1.2.42, upgrade to the most recent version of the isapi_redirect DLL.
Restart IIS.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector. There is no known workaround for IIS.

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Fri, 21 Dec 2018 13:55:16 GMT

Revision 21 posted to Appian Knowledge Base by Jordan Horwat on 12/21/2018 1:55:16 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the search-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices and restart the search server.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Fri, 21 Dec 2018 09:49:42 GMT

Revision 20 posted to Appian Knowledge Base by Jordan Horwat on 12/21/2018 9:49:42 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=X, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices and restart the search server.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Thu, 20 Dec 2018 15:51:48 GMT

Revision 19 posted to Appian Knowledge Base by Jordan Horwat on 12/20/2018 3:51:48 PM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices and restart the search server.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:59:04 GMT

Revision 18 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:59:04 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices and restart the search server.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:58:25 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:58:25 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices and restart the search server.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:45:33 GMT

Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:45:33 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade to the latest version of Apache and mod_jk connector:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:44:56 GMT

Revision 15 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:44:56 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:40:57 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:40:57 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:39:52 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:39:52 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, ensure that it is configured properly in the appian-topology.xml file(s) and start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:37:51 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:37:51 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to all versions of Appian using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:31:47 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:31:47 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running. If the search server is not running, start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to Appian 18.3 and later using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current User Activity is blank in the Admin Console with "Could not record user activity" warnings in the application server log

Jordan Horwat — Wed, 19 Dec 2018 11:29:52 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:29:52 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running without errors.
If the search server is not running, start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to Appian 18.3 and later using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current user activity is blank even after clearing the search indices

Jordan Horwat — Wed, 19 Dec 2018 11:28:34 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:28:34 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running without errors.
If the search server is not running, start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to immediately upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to Appian 18.3 and later using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current user activity is blank even after clearing the search indices

Jordan Horwat — Wed, 19 Dec 2018 11:27:06 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:27:06 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running without errors.
If the search server is not running, start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Affected Versions

This article applies to Appian 18.3 and later using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure

DRAFT KB-XXXX Current user activity is blank even after clearing the search indices

Jordan Horwat — Wed, 19 Dec 2018 11:26:17 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 12/19/2018 11:26:17 AM

Symptom

The Current User Activity tab in the Admin Console is blank. The following WARN message appears in the application server log:

WARN com.appiancorp.security.auth.activity.UserActivityFilter - Could not record user activity: secCtx=BPMSVC7, authDetails=AuthenticationDetails[ts=YYYY-MM-DD HH:MM:SS.MMM, entryPoint=PORTAL, clientIpAddress=XX.XX.XXX.XX, clientUserAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36] -- java.lang.NullPointerException

Cause

This issue can occur for the following reasons:

The search server is in a bad state.
The environment is using a version of Apache that is earlier than Apache 2.4, and the mod_jk connector version is earlier than 1.2.42.

Action

Ensure that the search server is running without errors.
If the search server is not running, start it according to the documentation.
If the search server is running, and the serach-server.log file located at <APPIAN_HOME>/logs/search-server/ contains errors, follow the Action section of KB-1082 to clear the search server indices.
If the above steps do not resolve the issue, or if the environment is using a version of Apache earlier than 2.4 and a mod_jk connector version earlier than 1.2.42, upgrade to the most recent version of Apache and the mod_jk connector.

Workaround

The following workaround has been identified in the case that it is not possible to upgrade the Apache and mod_jk versions:

Add the following lines to the bottom of the Apache httpd.conf file:

SetEnvIf Server_Addr "(.*)" AJP_LOCAL_ADDR=$1

JkEnvVar AJP_LOCAL_ADDR

Restart Apache.

Note: This workaround mimics the fix that is implicitly included in the mod_jk version 1.2.41. This workaround should not be a permanent solution, and the recommended course of action is to upgrade both Apache and the mod_jk to the most recent version and remove this workaround. Leaving this workaround as a long-term solution introduces potential risks if Apache were to change the behavior in that area of the connector in the future. This could expose the environment to problems on subsequent Tomcat versions that are distributed as part of Appian releases.

Affected Versions

This article applies to Appian 18.3 and later using Apache as a web server.

Last Reviewed: December 2018

Tags: apache, web server, search server, infrastructure