Clarity: DEBUG logging in Clarity 13.1 almost always results in message 'logging is not allowed for this action'

Article Id: 48805
Status: Published
Updated On: 14-02-2018 07:43
Legacy Id: TEC591657
Products:
CLARITY PPM FOR ITG CA Project & Portfolio Management CLARITY PPM FEDERAL CA Project & Portfolio Management SAAS STARTER PACK-CLARITY PPM
Issue/Introduction:

Description:

In Clarity 13.1, most logging categories return "logging is not allowed for this action" in the background (bg) service like this:

SYS 2014-03-13 20:24:22,670 [WrapperSimpleAppMain] niku.union (clarity:none:none:none) Starting Message Receiver on Event Manager
DEBUG 2014-03-13 20:24:22,667 [Post Condition Transition Pipeline 3 (tenant=clarity)] bpm.engine (none:none:none:none) * logging is not allowed for this action *
SYS 2014-03-13 20:24:22,679 [Event Interest Registration Thread] niku.union (clarity:none:none:none) Registering event interests...
DEBUG 2014-03-13 20:24:22,667 [Pre Condition Pipeline 0 (tenant=clarity)] bpm.engine (clarity:process_admin:2615892666__08B3E829-C553-4B3A-AD29-63A708C75F9C:none) * logging is not allowed for this action *
DEBUG 2014-03-13 20:24:22,667 [Post Condition Transition Pipeline 2 (tenant=clarity)] bpm.engine (none:none:none:none) * logging is not allowed for this action *

Steps to Reproduce:

  1. Log into the Clarity System Administration (CSA) application
  2. Configure DEBUG level logging for 'com.niku.bpm' component
  3. Restart the background services (BG)
  4. Initiate a Clarity BPM process

Expected Result: Informative logging messages in background log file.

Actual Result: Message 'logging is not allowed for this action' appears.

Solution:

WORKAROUND:

None.

STATUS/RESOLUTION:

CLRT-71365 : Resolved in Clarity 13.2

 

Environment:

Release: ESPCLA99000-13.1-Clarity-Extended Support Plus
Component: