This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Soft Skills and have John Sonmez on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes WLS8.1 serving old jsp pages after installing new ear file Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "WLS8.1 serving old jsp pages after installing new ear file" Watch "WLS8.1 serving old jsp pages after installing new ear file" New topic
Author

WLS8.1 serving old jsp pages after installing new ear file

debbie shifferd
Greenhorn

Joined: Oct 16, 2003
Posts: 11
We use Weblogic Server 8.1 SP4 on Sun Solaris. Typically, to install an upgrade to our web app - we bring Weblogic down, remove old package, install new package (via System V packaging pkgadd command), and restart Weblogic Server. Then once WLS is up, we test.

Last couple of installs, we have had to manually clear out the WLS cache files because WLS is serving up old pages instead of picking up the changes in our newly installed ear file.

We have never had to login to WLS console and hit redeploy button or anything else like that. It is our understanding that WLS should pick up the changes when you bounce it.

Are our assumptions wrong? Has anybody else had this problem and know why this is happening?
Ajay Reddy
Ranch Hand

Joined: Apr 08, 2005
Posts: 43
I have the same problem. Basically the old war file is cached by weblogic even after deploying the old war file. I have to manually remove the cached war file. The work around is when deploying a new war, deploy it with a new name(like test.build#.war).
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WLS8.1 serving old jsp pages after installing new ear file