Maybe I will try some more testing. The one thing I haven't replicated is that the problem machine is running 3 virtual hosts.
-----Original Message----- From: George Sexton [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2003 10:23 AM To: 'Tomcat Users List' Subject: RE: RequestDispatcher.include() on 5.0.14 I Emailed Remy off list. Essentially, the problem appears intermittent and may be hardware or JVM related (but I don't think so...). Here is the text of the last message I sent to him: You are right. I wrote a test case, and it worked. I then went back and re-tested my original application. This time it worked. Today, I ran into another problem where I was getting a ClassCastException retrieving an attribute from a session. When I run it under 4.1.29, it works perfectly. FWIW, Tomcat 5.0.14 was not doing this last night. There are many other places throughout the application where this attribute is retrieved from the session, but this is the only one failing. Just for grins, I made a small code change and re-compiled. Unsurpisingly the issue "went away" I just tried both issues on a different machine running 5.0.14 w/ JDK 1.4.1_01 under Windows and all aspects are working correctly. The machine where I have been having issues is running SUSE 9.0 professional with JDK 1.4.2-b28. I tried upgrading the JVM on the SUSE machine to 1.4.2_02-b03 and still had the same issues. This machine has been running Win2K reliably for several years. To be safe, I ran MemTest86 on it, and it reported no issues. At this point I have conflicting data. On the one hand, the app works on one machine with 5.0.14. On another machine, it doesn't work with 5.0.14, but works well with 4.1.29. At this point I have to say I believe there is something (or many things) wrong with 5.0.14. The problem appears intermittently, and is difficult to trigger with many different symptoms. -----Original Message----- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2003 9:10 AM To: Tomcat Users List Subject: RE: RequestDispatcher.include() on 5.0.14 At 07:32 PM 11/9/2003 -0700, you wrote: >I hate bugzilla. No, this appears to be a new item. Unsurprising really, >considering that it only fails in a root context. Then I assume you reported the bug? A link to the bug report would be helpful. Jake >-----Original Message----- >From: Jacob Kjome [mailto:[EMAIL PROTECTED] >Sent: Sunday, November 09, 2003 7:23 PM >To: Tomcat Users List >Subject: Re: RequestDispatcher.include() on 5.0.14 > > > >You should check bugzilla to see if there are already any reports like >this >for Tomcat-5. If not, report it. It might get lost if you just report >it >here. > >http://issues.apache.org/bugzilla/ > > >Jake > >At 03:55 PM 11/9/2003 -0700, you wrote: > >I have a servlet that does a pretty simple include: > > > >RequestDispatcher >rd=req.getRequestDispatcher("OutputCurrentWeek.html"); > >if (rd==null) { > > WebApp.log("Error getting RequestDispatcher for Include in > >ViewCal!",new Exception()); > >} else { > > rd.include(req,res); > >} > > > >This works on 5.0.14 if the application is not running in a ROOT > >context. If the app is in a ROOT context, it doesn't work. No exception > >is logged, so a non-null RequestDispatcher is returned, it just doesn't > >seem to work. I just verified that the application works correctly on > >4.1.29 for both ROOT and non-ROOT contexts. > > > >Is this an area where the spec changed, or is 5.0.14 broken? > > > > > >George Sexton > >MH Software, Inc. > >Voice: 303 438 9585 > >http://www.mhsoftware.com > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
