System environment: WebSphere 6.1.0.25 Network Deployment, with cluster, front end with IBM Http Server plugin things like this, because there are multiple applications on this cluster, you can not restart the app when updating the app Server. Also, in a clustered environment, if the app is updated directly, the app server restart in the was cluster is automatically triggered. So our habit of updating the app is to stop the app before uninstalling and then deploying the new version. After the implementation of this application update, there have been two such cases: after the deployment of the new application, the function is normal, is the style is all lost. Using Firefox's firebug tracking, it was found that the server gave the 503 Service unavailable response when requesting style.css. Check that the application deployment directory on the server, the physical files are in, access rights are normal, but it is not correct request to this file. searched a lot of documents and finally found the cause of the problem, Bug: pk80333:cannot DISPLAY A CERTAIN GIF file is the idea that when the app is stopping, In a short period of time, if the server receives a request for a static resource (CSS, JS, HTML, image, etc.), this static resource is identified by the server as permanently unavailable. Even if the application starts again and accesses this static resource, the server will also give a response to the 503 Service unavailable. However, there is no problem with dynamic resources such as JSPs and Servlets. This problem is fixed in 6.0.1.27. or, restarting the app Server will also restore. And, in a failed scenario, after the app starts, it's normal for a domain name to access this static resource. For example, the HTTP://XX.COM/STYLES/STYLE.CSS request arrives at the server exactly the moment the application stops, so all subsequent requests for HTTP://XX.COM/STYLES/STYLE.CSS will receive a 503 response. However, it is normal to change to a HTTP://XX1.COM/STYLES/STYLE.CSS request that points to the same address. The following is the original: problem summary************************************************USERS Affected:  IBM WebSphere application Server Version 6.1** and Version 7.0 users. ******************************************** Problem Description:all requests for a static file result * * &N Bsp in a ** servlet.has.become.temporarily.unavaila * * &NB Sp;ble.for.service exception. ****************************************************************** Recommendation:   ****************** When an application is being stopped a small timing windowexists during WH Ich, if a request for a static file isreceived, the static file would become permanently unavailableeven after the Applicat Ion has been restarted. Once the Staticfile have become permanently unavailable all requests for thefile would result in AServlet.has.become.tempora Rily.unavailable.for.serviceexception. The problem would persist until the server on Whichthe application was running is res Tarted. note the problem occurs for static files is and not, forexample, for Servlets and JavaServer Pages (J SPs). Problem conclusionthe Webcontainer have been modified to remove the timing WINDOWSO this a request for a static file during Application Stopcannot cause the static file to become permanently unavailable. the fix for this APAR is CurreNtly targeted for inclusion infix packs 6.1.0.27 and 7.0.0.5.
A 503 error occurred while requesting static resources after WebSphere update app
