Category - PO

1
SAP PO – temporarily out of MPI buffers -> roll out
2
SAP PO – how to increase the maximum number of application sessions
3
SAP PO – Semaphore error – e=28 semget No space left on device
4
PO – Exception of type java.sql.SQLRecoverableException caught: IO Error: The Network Adapter could not establish the connection
5
SAP PO – Deploying the SCA Using Telnet on the example of the last fix for Log4j
6
SAP PO – How to enable a handling of large messages in the Messaging System

SAP PO – Semaphore error – e=28 semget No space left on device

In dev_icm trace sometime You can find error like:

[Thr 140216781395712] *** ERROR => e=28 semget(3110149,60,2016) (28: No space left on device) [evtux.c 298]
[Thr 140216781395712] *** ERROR => EvtOpen(9000) failed: 1 [mpixx.c 6185][Thr 140216781395712] *** ERROR => EvtRst: Inv. Event Handle = 0 [evtux.c 1206][Thr 140216781395712] *** ERROR => EvtRst(0) failed: 2 [mpixx.c 6192][Thr 140216781395712] *** ERROR => IcmConnInitBuffer: MpiCreate2 failed (rc=MPI_EEVT: Event flag error/11) [icxxconn.c 5665]

Read More

SAP PO – How to enable a handling of large messages in the Messaging System

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).

Read More

Copyright © 2023. SAPBasisWorld.com Privacy Policy