Re: [JBoss-user] Showstopper Undeploy Problem??
- Original Message - From: "Jules Gosnell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 08, 2002 4:09 PM Subject: Re: [JBoss-user] Showstopper Undeploy Problem?? > Frank Morton wrote: > > More detail that may change your mind on the diagnosis. > > In addition to a jsp directory containing .jsp files, there > > were other directories, such as "graphics" and "css" that > > also did not show when looking at the content through > > the browser that were deployed as part of the same > > .war file. Restart jboss and everything is back leaving > > absolutely everything alone (ie, deploying the same .war > > file without replacing it). > > > > Different? > > > Jules Gosnell wrote: > > No. > > Restarting JBoss would redeploy every app to Jetty, which would rebuild > any temporary caches on disk. > > Simply touching the webapp that is displaying the problem would probably > have the same effect, since it would redeploy it. > > when you say "jsp directory created by deploying the .war file" exactly > which directory are you talkng about ? I am deploying the application as a .war file. In the .war file are the following directories: WEB-INF css graphics jsp properties template tmp Deploying the application works fine for a number of days, then suddenly 404 errors start coming up. The "jsp" directory contains all the .jsp files. When this condition occurs (ie, the 404 errors), if you look at the contents of the jsp directory through the browser, last time all .jsp files were gone with the exception of one. Additionally, a directory "include" within the jsp directory was also "missing" about half the files it normally contains. I later also noticed that the other directories, like "graphics" were also not showing. Restart jboss and all is ok again without any other changes. This has happened two times now in about 3 weeks. Since non-jsp files were also disappearing, that is what made me think it was more of a jboss/jetty issue and not a jsp specific issue. I don't see how precompiling jsp files would help graphics files from being undeployed. Thanks for your help. This one is a little unnerving. Frank --- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Showstopper Undeploy Problem??
Frank Morton wrote: > More detail that may change your mind on the diagnosis. > In addition to a jsp directory containing .jsp files, there > were other directories, such as "graphics" and "css" that > also did not show when looking at the content through > the browser that were deployed as part of the same > .war file. Restart jboss and everything is back leaving > absolutely everything alone (ie, deploying the same .war > file without replacing it). > > Different? > No. Restarting JBoss would redeploy every app to Jetty, which would rebuild any temporary caches on disk. Simply touching the webapp that is displaying the problem would probably have the same effect, since it would redeploy it. when you say "jsp directory created by deploying the .war file" exactly which directory are you talkng about ? Jules > > >>Jetty and Tomcat both use Jasper as their JSP engine. >> >>This is most likely a problem with Jasper, or some other process on your >>box cleaning up /tmp. >> >>If you are sure that no external process is screwing things up, then one >>way to avoid this happening would be to precompile your JSPs. >> >>This means that you will no longer be deploying any JSPs, but compiled >>Servlets. Then you will have no temporarily cached class files to worry >>about. >> >>advantages are: >> >>- compile-time errors will be caught in development, not production >>- deploying to a heavily loaded site will not cause multiple concurrent >>compilations of e.g. index.jsp (patch submitted to Jasper) >>- dispatch of request to servlet is simpler and therefore quicker since >>it goes direct from Jetty->Servlet and not Jetty-.Jasper->Servlet. >>- no compile environment needed on your production box - where it may be >>considered a security hazard. >> >>This FAQ contains an entry on JSP precompilation which I hope will be >>enlightening >> >> > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=H > EAD&content-type=text/vnd.viewcvs-markup > >> >>Jules >> >> >>Frank Morton wrote: >> >>>Jboss 3.0.0 >>>Linux/JDK 1.4.0 >>> >>>Second time this happened in about 3 weeks. >>>No error reported in any logs. >>> >>>Was running just fine, but started getting 404 errors like the url >>>didn't exist trying to display a commonly used jsp (logon page). >>> >>>If I look at the jsp directory created by deploying the .war file, >>>all of the jsps are gone except one and a directory. If I restart >>>jboss without touching the files in the deploy directory, things go >>>back to normal. >>> >>>Somehow deployed files are getting undeployed while the >>>server is running, even though the originating .war file is untouched. >>> >>>Is there any temporary solution to make an application >>>undeployable? I need help on this one. >>> >>>Thanks. >>> >>> >>> >>>, none of the jsp files look to be deployed now >>> >>> >>> >>> >>>--- >>>This sf.net email is sponsored by:ThinkGeek >>>Oh, it's good to be a geek. >>>http://thinkgeek.com/sf >>>___ >>>JBoss-user mailing list >>>[EMAIL PROTECTED] >>>https://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> >> >> >>--- >>This sf.net email is sponsored by:ThinkGeek >>Oh, it's good to be a geek. >>http://thinkgeek.com/sf >>___ >>JBoss-user mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-user >> > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Oh, it's good to be a geek. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Showstopper Undeploy Problem??
More detail that may change your mind on the diagnosis. In addition to a jsp directory containing .jsp files, there were other directories, such as "graphics" and "css" that also did not show when looking at the content through the browser that were deployed as part of the same .war file. Restart jboss and everything is back leaving absolutely everything alone (ie, deploying the same .war file without replacing it). Different? > Jetty and Tomcat both use Jasper as their JSP engine. > > This is most likely a problem with Jasper, or some other process on your > box cleaning up /tmp. > > If you are sure that no external process is screwing things up, then one > way to avoid this happening would be to precompile your JSPs. > > This means that you will no longer be deploying any JSPs, but compiled > Servlets. Then you will have no temporarily cached class files to worry > about. > > advantages are: > > - compile-time errors will be caught in development, not production > - deploying to a heavily loaded site will not cause multiple concurrent > compilations of e.g. index.jsp (patch submitted to Jasper) > - dispatch of request to servlet is simpler and therefore quicker since > it goes direct from Jetty->Servlet and not Jetty-.Jasper->Servlet. > - no compile environment needed on your production box - where it may be > considered a security hazard. > > This FAQ contains an entry on JSP precompilation which I hope will be > enlightening > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=H EAD&content-type=text/vnd.viewcvs-markup > > > Jules > > > Frank Morton wrote: > > Jboss 3.0.0 > > Linux/JDK 1.4.0 > > > > Second time this happened in about 3 weeks. > > No error reported in any logs. > > > > Was running just fine, but started getting 404 errors like the url > > didn't exist trying to display a commonly used jsp (logon page). > > > > If I look at the jsp directory created by deploying the .war file, > > all of the jsps are gone except one and a directory. If I restart > > jboss without touching the files in the deploy directory, things go > > back to normal. > > > > Somehow deployed files are getting undeployed while the > > server is running, even though the originating .war file is untouched. > > > > Is there any temporary solution to make an application > > undeployable? I need help on this one. > > > > Thanks. > > > > > > > > , none of the jsp files look to be deployed now > > > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Oh, it's good to be a geek. > > http://thinkgeek.com/sf > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Oh, it's good to be a geek. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Showstopper Undeploy Problem??
Jetty and Tomcat both use Jasper as their JSP engine. This is most likely a problem with Jasper, or some other process on your box cleaning up /tmp. If you are sure that no external process is screwing things up, then one way to avoid this happening would be to precompile your JSPs. This means that you will no longer be deploying any JSPs, but compiled Servlets. Then you will have no temporarily cached class files to worry about. advantages are: - compile-time errors will be caught in development, not production - deploying to a heavily loaded site will not cause multiple concurrent compilations of e.g. index.jsp (patch submitted to Jasper) - dispatch of request to servlet is simpler and therefore quicker since it goes direct from Jetty->Servlet and not Jetty-.Jasper->Servlet. - no compile environment needed on your production box - where it may be considered a security hazard. This FAQ contains an entry on JSP precompilation which I hope will be enlightening http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup Jules Frank Morton wrote: > Jboss 3.0.0 > Linux/JDK 1.4.0 > > Second time this happened in about 3 weeks. > No error reported in any logs. > > Was running just fine, but started getting 404 errors like the url > didn't exist trying to display a commonly used jsp (logon page). > > If I look at the jsp directory created by deploying the .war file, > all of the jsps are gone except one and a directory. If I restart > jboss without touching the files in the deploy directory, things go > back to normal. > > Somehow deployed files are getting undeployed while the > server is running, even though the originating .war file is untouched. > > Is there any temporary solution to make an application > undeployable? I need help on this one. > > Thanks. > > > > , none of the jsp files look to be deployed now > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Oh, it's good to be a geek. > http://thinkgeek.com/sf > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Showstopper Undeploy Problem??
Jboss 3.0.0 Linux/JDK 1.4.0 Second time this happened in about 3 weeks. No error reported in any logs. Was running just fine, but started getting 404 errors like the url didn't exist trying to display a commonly used jsp (logon page). If I look at the jsp directory created by deploying the .war file, all of the jsps are gone except one and a directory. If I restart jboss without touching the files in the deploy directory, things go back to normal. Somehow deployed files are getting undeployed while the server is running, even though the originating .war file is untouched. Is there any temporary solution to make an application undeployable? I need help on this one. Thanks. , none of the jsp files look to be deployed now --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
