trace jobs locking user via rfc

[Former Member]

Hello experts,

in our productive system we have a user especially for the sap oss support access. This user is getting locked every 2-3 minutes. The transaction sm20 shows these entries :

09.02.2012 15:02:53 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:03:18 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:03:53 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:04:18 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:04:53 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:05:18 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:05:53 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

09.02.2012 15:06:18 OSS-PB1 localhost SAPMSSY1 RFC/CPIC Login gescheitert, Grund=53, Typ=R 001 mlppb1

As far as i can see the terminal column says "localhost" --> this means the rfc connection is comming from the same "physical" machine. We've checked the ABAP stack, there is no job running using this user. Furthermore there is no rfc connection on the system itself using this user.

Is there a possibility to get more informations about the incoming rfc connection ? E.g., increasing the trace level.

It might be some rfc connection coming from the j2ee stack on this machine. Is there some way to check in the j2ee server if there were some regularly jobs ?

Our system is a SAP Netweaver BW 7.3 on SP 4.

Kind regards.

Dirk

[Former Member]

Hello,

thank you for your suggestion which sounds reasonble. Unfortunately we had to restart the j2ee server instances and afterwards the wrong login disappeared in the sm20. This may be a sign that the rfc connect was caused by some job running in the j2ee instance.

Kind regards.

Dirk

[isaias_freitas]

Hello Dirk!

Yes, if the errors stopped right after the j2ee was restarted, we can assume that it was some j2ee process / job that was causing the errors.

If the issue occurs again, look at the gateway trace as I've suggested, and you may find extra information that could help to solve it without a j2ee restart.

Regards,

Isaías

[isaias_freitas]

Hello Dirk!

You could increase the gateway trace level to 2, at the ABAP stack, wait for the connection to come, decrease the trace level, and analyze the dev_rd trace. If might give you additional information regarding the process that is performing the RFC calls.

You can look at the "TP" field of the incoming request. This could help you to at least find the process / application that is performing the calls.

I hope this helps!

Best regards,

Isaías