cancel
Showing results for 
Search instead for 
Did you mean: 

Error - 404 Application Not Found - Failed to process request

Former Member
0 Kudos

Hi team,


While accessing the java applications on NWA on PI 7.1 system , we get an error :


404  Application Not Found  SAP NetWeaver Application Server/Java AS 


Failed to process the request: Request refers to an unknown session


While clicking on the same , 2-3 times , although the error goes away , but appears again after sometime.

This is faced daily and comes on and off. Screenshot attached hereby.

Please let us know the resolution for the same.


Thanks,
Somya

Accepted Solutions (0)

Answers (1)

Answers (1)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

IMO, It happens the third case c.

the target system uses session and maintain your user credentials (login details). If the session timeout, the credentials are removed from the session and so when you click more than one time, it creates one on the target side and maintains again.  This session stays alive for some particular duration. If there is no trigger from interface the session fails and create one after your first call again. So you see this problem intermittently. Whenever you hit after a big pause, you see for the first call this problem and the target loads again your credentials and that takes delay and your subsequent call get connection.

Former Member
0 Kudos

We are getting this error even if we click on the page first time .....are there any parameters that we need to set to get this resolved.............................................it goes on an doff but we afce it frequently so how to resolve it...

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>We are getting this error even if we click on the page first time.

Yes if the session is the real issue then it happens mainly for the first time.  I would recommend this way.

If the target system requires session to be maintained to process the interface, then during rmapping you can simply sign on process first  and after successful logon then send the request. This two steps could help to avoid this problem.