Failed BEXANALYZER gateway errors stay in DISCONNECT state

Question

When I check SMGW I can see gateway errors for BEXANALYZER. Normally the parameter gw/conn_disconnect would cleanup these sessions (session w/ state of DISCONNECT). But this parm does not cleanup registered  server programs.
Any ideas how these can be removed?
AL08 will show "old" users - in this case failed RFC's so it is misleading.
Thank you.

Answer 1

Hello Agus
The error message indicates that the dispatcher process was not able to
deliver a NOWP message to a user context that does no longer exists.
This happens if a batch process issues an asynchronous RFC that shall
send a response when it finishes. However, the batch job does not wait
to collect the answer.
When the dispatcher tries to pass the result of the aRFC to the batch
process, it realizes that the context that issued the RFC no longer
exists and prints out the message.
YOu can safely ignore the message.
And for more information, Please refer to the notes:
27617     Syslog Q0G, scratch area too small
191234    Syslog: Q0G K request (type NOWP) cannot be ...
681085  Scratch area is too small, opcode 6
62239   Termination when maintaining syslog filters
This information should help a lot.
Regards,
Paul