cancel
Showing results for 
Search instead for 
Did you mean: 

WDA are not terminated when navigating throuth other iView/Page

Former Member
0 Kudos

Hi, experts!

Please help me with the following issue.

We’re facing a problem with the WDA (Webdynpro Abap) keeping the sessions active during the Portal navigation.

In our scenario, the user opens an ESS/MSS iView (which calls a Z Webdynpro Abap) and update some information about the employee.

Following, the user navigates to another iView in order to update another information, however the PERNR is locked by the other session.

If we navigate to the first iView, we can check the updated data displayed at the screen. Which means that session wasn’t terminated.

Looking at the transaction SM04, we can see the HTTP connections while the user navigates through Webdynpro Abap Aplications.

I’ve tried some adjustments like:

Tracking with the HTTPWatch I didn’t found the USER_ABORT command when navigating from one iView to another.

Could you please guide me on what should I do or review?

We’re on SAP Netweaver 7.4 SP 8

Thanks in advance!

Regards

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Luciano,

Are the portal and the backend are running on the same domain?

(E.g portal.domain.com is calling backend.domain.com)

What is the patch level of your 7.40 SP8 EP-RUNTIME SCA?

Best regards,

Etay

Former Member
0 Kudos

Hi, Etay, thanks for your reply!

    Portal and Backend are running on the same domain.

    It's the first time I'm looking at this... So I think we have not aplied any Patch Level. Could you please check the image below?

What other steps should I take?

Kind regards,

Luciano

Former Member
0 Kudos

Hi Luciano,

The blog

is the main blog for session termination issues from portal side.

The USER_ABORT (or USER_SUSPEND) should be sent when you navigate between different iViews.

Please check if SAPnote 2021994 is solving your issue.

Best regards,

Etay

Former Member
0 Kudos

Hi, Etay, thanks for your reply!

   We've updated the EP-Runtime patch level and everything worked fine!

   Thanks for your support!

Regards,

Answers (0)