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
JBoss-user@xxxxxxxxxxxxxxxxxxxxx
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
JBoss-user@xxxxxxxxxxxxxxxxxxxxx
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
JBoss-user@xxxxxxxxxxxxxxxxxxxxx
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
| 