AMXBPM upgrade to 3.1: Gadget application session is timing out after 30 minutes

Products	Versions
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM)	-

Description

We observed the following in the BPM logs:

25 Aug 2016 12:05:04,109 [http_httpconnector_tp_105 - /bpm/dispatch] [DEBUG] [amx.bpm.app] com.tibco.amx.governance.pa.pdp.PolicyDecisionPointImpl - Governed Object: uri==urn:amx:BPMEnvironment/amx.bpm.app/WorkManager/implementation.presentation/implementation.wpextender_1.7.0.001, Fully-qualified PEP: {http://tns.tibco.com/governance/policy/host}http/default/serviceInFlow, Actions to Execute: 1

25 Aug 2016 12:05:04,109 [http_httpconnector_tp_105 - /bpm/dispatch] [DEBUG] [amx.bpm.app] com.tibco.amx.governance.pa.pdp.PolicyDecisionPointImpl - Action to execute. Configuration Processor: {http://xsd.tns.tibco.com/governance/policy/action/2009}AuthenticationByJaas, Id: 803a88a0-f435-4c18-ba22-43d123b00f9d

25 Aug 2016 12:05:04,109 [http_httpconnector_tp_105 - /bpm/dispatch] [DEBUG] [amx.bpm.app] com.tibco.amx.governance.pa.pdp.PolicyDecisionPointImpl - Number of Actions To Execute: 1

25 Aug 2016 12:05:04,109 [http_httpconnector_tp_105 - /bpm/dispatch] [DEBUG] [amx.bpm.app] com.tibco.amx.governance.pa.pdp.PolicyDecisionPointImpl - TIBCO-OGS-GA-900709: Invoking Action To Execute. Action Id: 803a88a0-f435-4c18-ba22-43d123b00f9d, Configuration Processor: {http://xsd.tns.tibco.com/governance/policy/action/2009}AuthenticationByJaas

25 Aug 2016 12:05:04,109 [http_httpconnector_tp_105 - /bpm/dispatch] [DEBUG] [amx.bpm.app] com.tibco.amx.governance.agent.action.api.AbstractActionManager - Executing action: {http://xsd.tns.tibco.com/governance/policy/action/2009}AuthenticationByJaas at EnforcementPhase=serviceInFlow

25 Aug 2016 12:05:04,110 [http_httpconnector_tp_105 - /bpm/dispatch] [DEBUG] [amx.bpm.app] com.tibco.amx.governance.pa.action.authentication.celm.AuthenticationByCelmConnection - Unable to retrieve SOAP message for JAAS Authentication.

25 Aug 2016 12:05:04,110 [http_httpconnector_tp_105 - /bpm/dispatch] [ERROR] [amx.bpm.app] com.tibco.amx.login.failure - TIBCO-OGS_PA-901402: Authentication failed. Properties - [ RemoteHost=10.220.102.50, RemoteAddr=10.220.102.50, RequestURI=/bpm/dispatch ]

25 Aug 2016 12:05:04,110 [http_httpconnector_tp_105 - /bpm/dispatch] [INFO ] [amx.bpm.app] com.tibco.amx.governance.pa.action.authentication.AuthenticationAbstractAction - Authentication failed - No login credentials supplied.

25 Aug 2016 12:05:04,110 [http_httpconnector_tp_105 - /bpm/dispatch] [ERROR] [amx.bpm.app] com.tibco.amx.governance.agent.action.api.AbstractActionManager - Failed to execute action.

com.tibco.governance.pa.action.security.SecurityException: Policy enforcement failed to authenticate the request.

Issue/Introduction

AMXBPM upgrade to 3.1: Gadget application session is timing out after 30 minutes

Environment

OS: All Supported Operating Systems

Resolution

There is a defect AMRP-5264 fixed in AMX 3.3.0 hotfix 13.

-------------------------------------------------------------------------------------------------

Jetty provides a timeout mechanism for session expiry. The default value for the controlling parameter was hard coded to 1800 seconds. This inflexibility resulted in inconvenience for users. With this fix, a session's maximum inactive interval is now configurable by setting the

"com.tibco.amf.hpa.tibcohost.jetty.sessionMaxInactiveIntervalInSecs" TRA property in the Node's TRA file as follows:

java.property.com.tibco.amf.hpa.tibcohost.jetty.sessionMaxInactiveIntervalInSecs=1800

The default for this property is 1800 seconds.

Ensure that AMX 3.3.0 hotfix 13 is installed in the environment and add the following parameter in the BPMNode tra file.
Set appropriate timeout value and restart the host with the "-clearCache" option.

java.property.com.tibco.amf.hpa.tibcohost.jetty.sessionMaxInactiveIntervalInSecs=1800

Additional Information

AMX 3.3.0 HF13 readme documentation

Welcome to "KB Articles"