Re: Java 1.4.2_08 and up breaks Jstl
page in the browser by the way. You might thing ok there is something wrong with the User class. So I added some extra lines before the jstl call: % // Person is a super class of User so casting the object to a Person object will do. Person person = (Person)session.getAttribute(person); System.out.println(Language = + person.getLanguage().getLocaleName()); % Language = EN appears in the catalina out, so you can conclude that the jsp code can read the Language locale name in User but jstl cant. I then had /opt/java point back to /opt/j2sdk1.4.2_05 and restarted tomcat. I then call the same webpage and the now the page works. My conclusion is that jstl in combination with j2sdk 1.4.2_08 or higher is impossible. For some reason they wont work together. Thanks in advance for any help you could offer, Martyn It would probably help, if you would describe what you did (i.e. what is your source code, your environment, tomcat version , etc.) and what does mean the bug happens (i.e. error messages, stack traces, etc.) Now we have just the analogue of My car works on road a but not on road b. Do you know what is wrong? Christoph Martyn Hiemstra wrote: Hi Do you have a link to a Sun Bugparade entry describing the problem? No I don't. I have performed a test of my own. I have installed j2sdk 1.4.2_05 and j2sdk 1.4.2_08 and j2sdk 1.4.2_09. I have installed these to the /opt directory. I have my JAVA_HOME pointed to /opt/java. First I point /opt/java to /opt/j2sdk1.4.2_09 and restart tomcat. The bug happens again. I then point /opt/java to /opt/j2sdk1.4.2_08. I restart tomcat and the same bug occures. I then point /opt/j2sdk1.4.2_05 to /opt/java, restart tomcat and BINGO no bug. Apparently versions java 2 sdk 1.4.2_09 and java 2 sdk 1.4.2_08 cause the bug to occure just as in the forum thread. I have tried a different tomcat version but no luck. Any ideas anybody? Maybe a configuration change that has occured in the new java versions? Martyn Hi, I'm not convinced by that forum thread. It's very hard to believe that there is such a severe bug in Java 1.4.2_06 *that isn't fixed yet* Do you have a link to a Sun Bugparade entry describing the problem? Christoph Martyn Hiemstra wrote: Hi All I have found a Bug in Java 1.4.2_08 and Java 1.4.2_09. Goto this address to read about it: http://forum.java.sun.com/thread.jspa?threadID=599301tstart=0 The new versions will break your jstl code and create errors in the log and create blank pages. I have tried a new Tomcat version, no luck. I had it running on another server but that server is running on Java 1.4.2_05. So just a tip. Dont install Java 1.4.2_08 or higher. It will kill your application if your using jstl. Martyn - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Java 1.4.2_08 and up breaks Jstl
Hi All I have found a Bug in Java 1.4.2_08 and Java 1.4.2_09. Goto this address to read about it: http://forum.java.sun.com/thread.jspa?threadID=599301tstart=0 The new versions will break your jstl code and create errors in the log and create blank pages. I have tried a new Tomcat version, no luck. I had it running on another server but that server is running on Java 1.4.2_05. So just a tip. Dont install Java 1.4.2_08 or higher. It will kill your application if your using jstl. Martyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java 1.4.2_08 and up breaks Jstl
Hi Do you have a link to a Sun Bugparade entry describing the problem? No I don't. I have performed a test of my own. I have installed j2sdk 1.4.2_05 and j2sdk 1.4.2_08 and j2sdk 1.4.2_09. I have installed these to the /opt directory. I have my JAVA_HOME pointed to /opt/java. First I point /opt/java to /opt/j2sdk1.4.2_09 and restart tomcat. The bug happens again. I then point /opt/java to /opt/j2sdk1.4.2_08. I restart tomcat and the same bug occures. I then point /opt/j2sdk1.4.2_05 to /opt/java, restart tomcat and BINGO no bug. Apparently versions java 2 sdk 1.4.2_09 and java 2 sdk 1.4.2_08 cause the bug to occure just as in the forum thread. I have tried a different tomcat version but no luck. Any ideas anybody? Maybe a configuration change that has occured in the new java versions? Martyn Hi, I'm not convinced by that forum thread. It's very hard to believe that there is such a severe bug in Java 1.4.2_06 *that isn't fixed yet* Do you have a link to a Sun Bugparade entry describing the problem? Christoph Martyn Hiemstra wrote: Hi All I have found a Bug in Java 1.4.2_08 and Java 1.4.2_09. Goto this address to read about it: http://forum.java.sun.com/thread.jspa?threadID=599301tstart=0 The new versions will break your jstl code and create errors in the log and create blank pages. I have tried a new Tomcat version, no luck. I had it running on another server but that server is running on Java 1.4.2_05. So just a tip. Dont install Java 1.4.2_08 or higher. It will kill your application if your using jstl. Martyn - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Same servlets in 2 contexts. Update 1 of them, not reloaded on context reload
Hi All, I am having a problem with Tomcat. I have a website application that I use over 2 aplications. 1 context I use for testing and the other is meant for vistors (live version). This means that the same application is running over 2 contexts . When I update a servlet in the test context and then reload the test context the update isnt loaded. For example: I have the exact same servlet in the test and live context. I then update the servlet in the test context by adding the following code System.out.println(Updated servlet); to the doGet function of the servlet. I then reload the test context. The situation at this point is that the test context has the updated servlet and that the live context has the older version of the servlet. When the servlet is executed in the test context the text 'Updated servlet' doesnt appear in the catalina.out file. If the servlet had been reloaded correctly then the test context should have printed 'Updated servlet' to the catalina.out file everytime the servlet is executed (Called via the get method). This makes me beleive that there is something very wrong with tomcat, that it cant keep a clear difference between the same servlet (although slightly modified) over different contexts. I am using jakarta-tomcat-5.0.27 and j2sdk1.4.2 on debian sarge. A tomcat restart by the way does solve the problem but thats not a solution for me. Thanks, Martyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat cant handel pressing F5 a couled of times
Hi All I beleive I may have found a major flaw in Tomcat 4, 5.0 and 5.5 I have created a numerous amount of applications and deployed them. After a page has loaded I press F5 5 times. This causes tomcat to CRASH I have tried Tomcat 4, Tomcat 5, Tomcat 5.5 all with different java versions. I have disabled all the filters in my application. Every possible combination will crash tomcat if you perss F5 more than 5 times fast. If you are running tomcat please try it and let me know if tomcat crashes and with which version. After looking for hours I found a filter that catches all the incoming requests. Each request is put in a queue and the first and last request is let through, the rest is thrown away. This seems to work. Has anybody else got this problem? Martyn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
