Category - PO

In last time, i.e. 11.01.2022 SAP released Log4j 2.17.1 update for SAP NetWeaver Process Integration. With this update all currently known Log4j vulnerabilities are fixed. More information You find in note: 3135581 and below You find  solution how to implement this fix.

You have to remeber. Concurrent processing of large messaging in the messaging system queue could lead to out of memory errors due to heap being exhausted. A message is considered to be #large# if it exceeds the threshold for large messages. In order to be processed, the message must have a specific number of permits (the number of permits is the message size divided by the threshold).

Today we have this situation… It’s not possible to clear the ICM server cache. In SAP logs like defaultTrace.trc You can find below entries:

You have set up an SSL port in the AS Java, but You see the following message in the SSL wizard on NWA: SSL port “XXXXX”: not active – where XXXXX is the port number. How to set up SSL You can find information here but below You find the solution the solution for the mentioned error.

Sometimes You can observe application is not accessible or server nodes hang. The dbpool connection error below logged into the server default traces.