FF user locked.

[dsanpor]

Dear Experts:

On my system there is a regular issue..

Example:

A user can access USER_A user with a Fire Fighter USER_FF system.

If USER_A leaving the system before going to the Fire Fighter USER_FF user. This Fire Figthter user is blocked.

I expected the system timeout or communications force logout.

However it is not produced logout of Fire Fighter user.

Is there any system parameter to put a time limit on this connection?

On my system:

u2022 rdisp / gui_auto_logout log off = 1800 sec

If it is comunication connectión: rdisp/keepalive = 1200 sec

Thanks and regards David Sanchez.

[dsanpor · Accepted solution]

No this is not the problem.

I repeat de example:Example:

A user can access USER_A user with a Fire Fighter USER_FF system.

If USER_A leaving the system before logout the Fire Fighter USER_FF user. This Fire Figthter user is blocked.

The the system shows 2 dialogs en AL08. One dialog with USER_FF and the other dialog with USER_A.

Notes:

- If I wait timeout. These processes remain in the system. They do not affect any time out as defined in the system.

- If USER_A try to access with USER_FF then the system response with message "FF user is in use".

I can solve this issue:

- If i kill dialog mode of USER_A then de dialog mode of USER_FF die. If I kill dialog mode USER_FF then dialog mode USER_A die.

If User_a leave the system before user_ff. User_ff will be locked. In the desktop of USER_A there are not windows with USER_FF because this mode die. However the systema keep dialog mode with USER_FF and this dialog mode locks all

future logon of every user ( USER_A included ).

I need a system parameter or other procedure witch allows to unlock USER_FF.

Thanks and regards David Sánchez.

[Former Member · Accepted solution]

Hi David,

Are you able to find out what the firefighter is doing in this time? As surpreet suggested, it might be processing a batch job. Hence it is locked, or it might be locked out doing an update. Trying trace on this user id and see what it does when you have logged off might help you narrow your problem.

Regards,

CP

[Former Member · Accepted solution]

<<<<<I need a system parameter or other procedure witch allows to unlock USER_FF.>>>>>>>>

there is no such parameter or procdure.

this is standard SAP funvtionality of Logoff, SPM had not added any extra code for this.

subroutine ..... get_user_sessions......

is used for checking same..... kindly take help of your developers to understand this routine.....

it first user th_server_list, to get list of all the app servers and then use another standard SAP function module if user is in use or not.

both are standard SAP FM's .......

regards,

Surpreet

[dsanpor]

Thank´s for you help.

There is not locks in SM13, SM12.

In SM37 with FF_USER there is any process.

In SM50 / SM51 there is any process.

I can see only two modes ( sm04/al08) open and have no activity. FF_USER the first with the second user to call the FF_USER. Are linked because FF_USER kill kill the user mode call it. You can block and remain the same time. Ie the start and the end is the same.

This only occurs the user is FF_USER call made before the FF_USER logoff.

I understand that perhaps this is the standard functionality.

Thank you very much for your help.

A greeting.

David Sánchez.

[dsanpor]

Hello,

I don´t know if I should write here real data of server, address ....

There are 3 application servers.

Thanks and regards.

David Sánchez.

NAME HOST SERV MS HOSTADR SERV ST HOSTNAMELONG

server1p_sid_01 server1p sapdp01 BB ADDR37AF 0C81 01 server1p

server0_sid_00 server0 sapdp00 BF ADDR3770 0C80 01 server0

server2_sid_03 server2 sapdp03 BB ADDR375C 0C83 01 server2

HOSTADDR_V4_STR HOSTADDR_V6_STR SY SY SY SY

XXX.XX.XX.XX0 XXX.XX.XX.XX0 00 00 00 00

XXX.XX.XX.XX1 XXX.XX.XX.XX1 00 00 00 00

XXX.XX.XX.XX2 XXX.XX.XX.XX2 00 00 00 00

Edited by: David Sanchez on Oct 4, 2010 12:49 PM

[Former Member]

David,

at must of customer system, i found that entry in service file was missing

so this FM tells if it is

however it is maintained in your case

so .... i will suggest you use below workaroud

when you see the FF locked :

1. click refresh button

2. click message button and send message to locked id

hope this help

regards,

Surpreet

[dsanpor]

Thanks experts:

This FF user not execute reports during a long time. The logs shows.

SMEN

ZACU_OPVIN_VISUALIZA ( in st03n i saw its time is 146 seconds)

SESSION_MANAGER

FBL3N

Oss note 1290018 says: "This is standard SAP behavior and the same goes for the Firefight ID. If the Firefight session is not closed properly and is interrupted, SAP will still think the FirefightID is still in use until the system is able to clear the session."

When the system is able to clear the session?

Fire Fighter user has locked during 6 hours. But logoff parameter has only 1800 seconds.

However, it is true, this user does not log off properly. This user make logon when another session was opened.

Best regards

David Sánchez.

[Former Member]

David,

Can you please copy paste output of function module SE37 -> TH_SERVER_LIST -> F8 -> F8

regards,

Surpreet

[Former Member]

David,

the FF id which get locked, does it execute any BDC or Batch job after logging in FF

if yes, then it is correct that this user remains locked

there might be UPDATE running in the name of this FF id, hence per design FF will keep it locked.

regards,

Surpreet

[sunny_pahuja2]

Hi,

This is standard system behavior, if you finds this then you can kill session from SM04.

Check SAP note 1290018 for more info.

Thanks

Sunny