PEGA0014 alert: Inbound mapping time exceeds limit

After a service receives and processes a request, the request data is mapped from the inbound request into Process Commander properties. The PEGA0014 alert is triggered when the elapsed time required for mapping the data from the request exceeds the threshold setting.

As of Version 5.3, this alert and its corresponding settings are deprecated. In Version 5.3 and later, the elapsed time for response mapping is included within the elapsed time reported in the PEGA0011 alert.

Example message text

Service inbound mapping request time has exceeded the threshold of 500 ms: 9072 ms

Default prconfig.xml settings

<env name="alerts/services/inboundMappingTime/enabled" value="false" />

Toggles the alert on ("true") or off ("false").

<env name="alerts/services/inboundMappingTime/threshold" value="500" />

The default threshold setting is 500 milliseconds (1/2 second). This setting measures elapsed (total) time, not just CPU time.

Reason for the alert

This alert usually means that the incoming service request is passing a lot of data. If the time spent is excessive, make sure that the mapping in the service rule is entered correctly. If a lot of data is arriving in the request, examine how the request is structured and whether all the data needs to be included.

Related Content

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.