-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 8.2
-
Component/s: Actions & Filters
-
Epic Link:
-
Tags:
-
Impact type:Configuration Change
-
Upgrade notes:
-
Team:AT
-
Sprint:nxAT Sprint 8.3.2
-
Story Points:2
Since NXP-18951, the ActionService can show slow actions/filters rendering, using a custom property stating the number of seconds threshold.
This custom property is not retrieved properly from configurations held by the nxserver/config folder, because the static field is initialized before deployment of the configuration files.
Also, the ActionService, FaceletDebugHandler and JSFDebugPhaseListener are not using consistent log levels for debug (some are using the INFO level).
Corresponding sample log4j configuration:
<category name="org.nuxeo.ecm.platform.ui.web.util.FaceletDebugTracer"> <priority value="DEBUG" /> </category> <category name="org.nuxeo.ecm.platform.actions.ActionService"> <priority value="DEBUG" /> </category> <category name="org.nuxeo.ecm.platform.ui.web.rest.JSFDebugPhaseListener"> <priority value="DEBUG" /> </category>
See also attached sample runtime configuration enable-jsf-debug-config.xml
that can be placed in nxserver/config to configure threshold times for ActionService and FaceletDebugTracer:
<?xml version="1.0"?> <component name="org.nuxeo.ecm.platform.enable.jsf.debug.config"> <require>org.nuxeo.ecm.platform.ui.web.configuration.default</require> <require>org.nuxeo.ecm.platform.actions.ActionService.properties</require> <extension target="org.nuxeo.runtime.ConfigurationService" point="configuration"> <property name="nuxeo.jsf.debug.log_min_duration_ms">20</property> <property name="nuxeo.actions.debug.log_min_duration_ms">5</property> </extension> </component>
- depends on
-
NXP-18951 Add timers to evaluate costly rendering calls
-
- Resolved
-
