Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

2022-02-27 2771052

2771052 - PI global parameter of retention period for


logging messages is not taking effect
Version 1 Type SAP Knowledge Base Article
Language English Master Language English
Release Status Released to Customer Category Problem
Component BC-XI-CON-MSG (Messaging System) Released On 02.04.2019

Please find the original document at https://launchpad.support.sap.com/#/notes/2771052

Symptom

In NWA, you configured parameter messaging.log.retainTime for synchronous/asynchronous messages


that being set logging, however, when you check relevant messages, this global parameter of retention
period is not taking effect. For example, no matter what's value the parameter is configured to, the actual
message retention period is not changed at all. The parameter is not working. You can check
PERSIST_UNTIL filed via following SQL query:

select MSG_ID, PERSIST_UNTIL from <SAP JAVA DB SCHEMA>.BC_MSG_LOG where MSG_ID =


'sample message ID'

Environment

• SAP enhancement package 1 for SAP NetWeaver 7.3 SP 12 or higher


• SAP NetWeaver 7.4 SP 07 or higher
• SAP NetWeaver 7.5

Reproducing the Issue

1. Change the parameter messaging.log.retainTime in NWA;


2. Execute SQL query for sample message;
3. You will notice the retention period is not getting changed.

Cause

You have configured the message retention for message belonging to specific interfaces based on the
message header attributes, i.e. sender party, sender service, interface name, interface namespace, receiver
party and receiver service. The configuration is performed in SAP NetWeaver Administrator or PIMON via a
new user interface: "Message Retention". This retention period is of higher priority than
messaging.log.retainTime, also wild card (*) can be used for any of the message header attributes.

Hence, if you set wild card (*) for all message header attributes, and set retention period for 1 day, then it
would take effect on all asynchronous and synchronous messages that being set logging. Parameter
messaging.log.retainTime is overwrote.

Resolution

1. If you would like to use interface specific retention period, you can set it in NWA -> SOA -> Monitoring -
> Message Retention; as note 1960448 - Configure message retention period per interface;
2. If you would like to use global parameter of retention period, then delete the interface specific retention
period rule;

© 2022 SAP SE or an SAP affiliate company. All rights reserved 1 of 2


2022-02-27 2771052

3. If online change of parameter messaging.log.retainTime is not working, please follow KBA 2423740 -
Parameter "messaging.log.retainTime" is not activated after configuration

See Also

2565934 - Service property messaging.log.retainTime requires system restart to become effective

Keywords

retention period, persist duration, not working, not taking effect, overwrite, bypass, messaging.log.retainTime,
Message Retention, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process
Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX

Products

SAP NetWeaver 7.4


SAP NetWeaver 7.5
SAP enhancement package 1 for SAP NetWeaver 7.3

Other Components

Component Description

BC-NWA-XPI Process Integration (PI) Monitoring

This document refers to

SAP Note/KBA Title

2423740 Parameter "messaging.log.retainTime" is not activated after configuration

2565934 Service property messaging.log.retainTime requires system restart to become effective

1960448 Configure message retention period per interface

Introduction of the tables that keep message related data in the database of PI/PO system

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2022 SAP SE or an SAP affiliate company. All rights reserved 2 of 2

You might also like