In some shops that 404 error page in IIS is pointed to an error handler page in the servlet container. If you are doing that and IIS was updated by a user or an automatic update from MS updates the 404 parameter could have been changed back to point to the original 404.htm known by IIS. (my experience).
Bryan LaPlante ----- Original Message ----- From: "Mousmi Bansal" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 10, 2003 9:51 AM Subject: JRun application suddenly stopped working > We have an application that uses JRun and IIS. The > application has JSPs, servlets, java beans as well as > stored procedures. Database is MS-SQL Server. The > entire application was working well... till now. > Suddenly the main login page has started throwing a > 404 error (and of course if we are not able to login, > there is no way we can access the rest of the > application). We renamed a regular HTML page and saved > it with .JSP extension. And then we couldn't make it > come up either. Essentially no JSP pages are being > served. > > Due to pecularity of our situation, we have limited > access to production server. But the sys admin has > told us that no upgrades were performed on the machine > nor was any configuration changed. global.properties > and local.properties SEEM fine. No libraries SEEM to > be missing. > > We looked through the default-event.log and see the > following messages- > > > 06/06 10:06:05 info (JRun) Loading monitor > 06/06 10:06:05 info (JRun) Loading license > 06/06 10:06:05 info (license) Enabling unlimited > concurrency for Advanced > 06/06 10:06:05 info (JRun) Loading control > 06/06 10:06:05 info (control) control listening on > 127.0.0.1:53000 > 06/06 10:06:05 info (JRun) Loading ejb > 06/06 10:06:05 warning (ejb) EJB service not starting, > enterprise key not found. > 06/06 10:06:05 info (JRun) Loading jms > 06/06 10:06:05 error (jms) Can not create JNDI initial > context: Need to specify class name in environment or > system property, or as an applet parameter, or in an > application resource file: > java.naming.factory.initial > 06/06 10:06:05 info (JRun) Loading jndi > 06/06 10:06:05 info (JRun) Loading jdbc > 06/06 10:06:05 info (JRun) (MYAPP) Initializing JDBC > connection pool with 0 connections > 06/06 10:06:05 warning (jdbc) Binding exception: Need > to specify class name in environment or system > property, or as an applet parameter, or in an > application resource file: > java.naming.factory.initial > [javax.naming.NoInitialContextException: Need to > specify class name in environment or system property, > or as an applet parameter, or in an application > resource file: java.naming.factory.initial] > javax.naming.NoInitialContextException: Need to > specify class name in environment or system property, > or as an applet parameter, or in an application > resource file: java.naming.factory.initial > at > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:640) > at > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) > at > javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:280) > at > javax.naming.InitialContext.bind(InitialContext.java:355) > at > allaire.jrun.sql.JdbcBindingService.init(JdbcBindingService.java:98) > at > allaire.jrun.ServletService.init(ServletService.java:66) > at > allaire.jrun.ServletService.init(ServletService.java:31) > at > allaire.jrun.servlet.JRunServletLoader.loadServletInstance(JRunServletLoader .java:203) > at > allaire.jrun.servlet.JRunSE.initService(JRunSE.java:892) > at > allaire.jrun.servlet.JRunSE.initServices(JRunSE.java:859) > at > allaire.jrun.servlet.JvmContext.initServices(JvmContext.java:130) > at allaire.jrun.servlet.JRunSE.init(JRunSE.java:223) > at > allaire.jrun.servlet.JvmContext.init(JvmContext.java:69) > at > allaire.jrun.ServletService.init(ServletService.java:66) > at > allaire.jrun.ServletService.init(ServletService.java:31) > at JRun.main(JRun.java:172) > 06/06 10:06:06 info (JRun) Loading web > 06/06 10:06:06 info (web) web listening on *:8100 > 06/06 10:06:06 info (JRun) Loading mail > 06/06 10:06:06 info (JRun) Loading url > 06/06 10:06:06 info (JRun) Loading default-app > 06/06 10:06:06 info (default-app) Starting > default-app: Default User Application - Default > application for getting started > 06/06 10:06:06 info (default-app) Loading scheduler > 06/06 10:06:06 info (JRun) Loading session > 06/06 10:06:06 info (default-app) Loading logging > 06/06 10:06:06 info (session) Loading persistence > storage provider 'file' > 06/06 10:06:06 info (JRun) Loading authentication > 06/06 10:06:06 info (JRun) Loading propfile > 06/06 10:06:06 info (JRun) Loading jsp > 06/06 10:06:06 info (JRun) Loading file > 06/06 10:06:06 info (JRun) default-app Ready > 06/06 10:06:06 info (JRun) Loading demo-app > 06/06 10:06:06 info (demo-app) Starting demo-app: JRun > Demo - JRun Demo > 06/06 10:06:06 info (demo-app) Loading scheduler > 06/06 10:06:06 info (demo-app) Loading logging > 06/06 10:06:06 info (JRun) Loading session > 06/06 10:06:06 info (session) Loading persistence > storage provider 'file' > 06/06 10:06:06 info (JRun) Loading authentication > 06/06 10:06:06 info (JRun) Loading propfile > 06/06 10:06:06 info (JRun) Loading jsp > 06/06 10:06:06 info (JRun) Loading file > 06/06 10:06:06 info (JRun) demo-app Ready > 06/06 10:06:06 info (JRun) Loading MYAPP > 06/06 10:06:06 info (MYAPP) Loading scheduler > 06/06 10:06:06 info (MYAPP) Loading logging > 06/06 10:06:06 info (JRun) Loading session > 06/06 10:06:06 info (JRun) Loading authentication > 06/06 10:06:06 info (JRun) Loading propfile > 06/06 10:06:06 info (JRun) Loading jsp > 06/06 10:06:06 info (session) Loading persistence > storage provider 'file' > 06/06 10:06:06 info (JRun) Loading file > 06/06 10:06:06 info (JRun) MYAPP Ready > 06/06 10:06:06 info (JRun) Loading jcp > 06/06 10:06:06 info (jcp) jcp listening on > 127.0.0.1:51000 > 06/06 10:06:06 info (JRun) default Ready > > So, how can an application work well one day and > suddenly stop working the next ? Would anybody know > the possible causes for receiving such error messages > and the application throwing a 404 ? > > I looked through one of the technical articles on > Macromedia website and it mentioned the variable > <app-name>.use-webserver-root. The development server > also uses the IIS and I looked through the > local.properties file. It does not have this variable > set, which means it is "false" by default, which, in > turn, means that JRun should serve pages relative to > its root. Since our pages are in IIS root, this SHOULD > generate 404 error BUT IT DOESN'T. The application > works just fine on development. I explicitly set the > variable MYAPP.use-webserver-root = false so that JRun > throws error but it still served the pages correctly > in dev env. Not sure what is happening... > > One of the things I noticed on the PRODUCTION > local.properties file is that it does not have the > line ejb.ejipt.enableMessaging=true. They are using > advanced edition. Could this be causing the problem ? > > > Thanks for your help. > > > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com > > =========================================================================== > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". > > Some relevant archives, FAQs and Forums on JSPs can be found at: > > http://java.sun.com/products/jsp > http://archives.java.sun.com/jsp-interest.html > http://forums.java.sun.com > http://www.jspinsider.com > =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
