Hello,
I am aware that many questions related to same "400 Session not found" have been asked/discussed in many threads on SCN.
To name a few: -
Re: 400 session not found : Failed to process the request
parallel login to nwa of netweaver 7.3
SAP Notes seen:
1464914 - JSESSIONID cookie value is unexpectedly changed by the server
1395551 - Global configuration of session cookies
My Portal version : CE7.3 EHP1 SP9
However, I wanted to ask some more questions and share my observations and seek your opinion: -
1. I have observed that this error (attached screenshot) comes when: -
a. I open any Web Dynpro java application, (be it Content Admin, User Admin or any of my custom Web Dynpro Java app) and keep it idle for some 30-40 seconds.
b. And then I click on any link/actionable UI on these idle application.
2. From these threads, I also understand that this is normal behavior as application has expired due to long idle time and session cookie sent to server is invalid. Fair enough.
3. But our end users are not happy to see such error trace page and its causing lot of incidents/complaints.
Is there any way to: -
A. Make Portal server to accept request coming from such timed-out/idle application?
B. Replace this error page with something more descent page?
Thanks & Regards,
Amey Mogare