Caching Issue For Redeployment Of JSP
(Doc ID 1324308.1)
Last updated on SEPTEMBER 29, 2020
Applies to:Oracle WebLogic Server - Version 10.3.3 to 10.3.6
Information in this document applies to any platform.
After a new JSP file has been added to the application, when we try to access the JSP, a 404 error is thrown (which should not be the case). However, when we stop and start the application, the JSP is accessible. Issue is reproducible by following these steps:
- Try to access any JSP page which does not exist in the application module.
- Now try to access it from both servers in the cluster.
- We will get 404 error, as the module does not exist.
- Now create a new JSP page and usingweblogic.deployer -redeploy, deploy the JSP page.
When you try to access the JSP page, you still will not able to access it. To overcome this issue, we need to stop and start the application module, after which the JSP file can be accessed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document