Skip to Content
avatar image
Former Member

Portal Session Not Ended Immediately in Backend Causing ENQ Lock

Background:

We have a customized effort logging program running under Portal. When the user decides not to save the change and just click "logoff" from portal to exit without change.

Normal Situation:

Normally, the user session will be terminated immediately in backend once the user logs off portal. This will then automatically clean up all session buffer and application ENQUEUE via ABAP webdynpro Controller routine.

Problem Situation:

Occasionally, it is found that the session is not terminated immediately in ECC backend system. The session still exists in ECC under SM04 and the previous ENQUEUE still exists in the ENQUEUE table under SM12.

When the user logs back into the portal to perform the effort logging again immediately after, the application will have error complaining the employee still locked in the ENQUEUE table by the previous transaction.

Such leftover session will be automatically cleaned up by ECC backend system after 30 minutes timeout. Even no action is done, the user can resume to the Effort Logging function after 30 min. after the record is locked.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Sep 04, 2008 at 07:38 PM

    Configure the DSM terminator.

    --Vishal

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 01, 2008 at 04:47 PM

    Hello,

    We are facing the same problem. Could you please let us know the solution for this issue?

    Thank you,

    Nikee

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 02, 2008 at 10:30 PM

    Ghatmaneni,

    What kind of custom application is causing these sessions to lock up in the backend? ( ie.. BSP, WebDynpro, JSP)

    Add comment
    10|10000 characters needed characters exceeded