RE: Tomcat reboot runtime
If I remember rightly, the Enhydra Multiserver allowed you to restart the server from the web based administration console. Enhydra was tomcat based I believe.. So how did they achieve this (I don't know.. It's possible they weren't fully stopping the JVM and starting a new process) They also allowed you to stop from the HTML console which, obviously, made restarting it again a little tricky from the admin console.. I guess they thought it was easier than typing multiserver -stop from a command line?? We did it using shell scripts on our servers.. The tomcat process is protected by a restart script anyway (we found that some native libraries can completely screw up the JVM, causing memory errors and exit - its rare but we just need the container to restart in these situations). So we have a stop script that attempts to stop tomcat the nice way, a kill script and restart and start scripts... These are just called from an admin console that runs outside of the tomcat (PHP). Regards, Matthew -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 14 May 2004 14:30 To: Tomcat Users List Subject: RE: Tomcat reboot runtime NB As a relative novice to Tomcat it astonishs me that the Tomcat Manager does not provide the functionnality to reboot the server at runtime (taking in account that it services become unavailable during reboot time). Show me a server that does. Nearly all let you reload apps, some let you update JNDI entries etc, a few let you add new connectors etc., but a complete reboot meaning a new JVM process is different. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
RE: Is .24 stable?
Hi Andi, Just thought I'd let you know that we upgraded our development systems to .24 a couple of days ago and have only seen improvements. We just copied our common libs over, changed CATALINA_HOME and dumped the WAR files in the webapps folder.. We were up and runnning in seconds... Our apps use many features of the container as well as several external libraries which have been known to crash tomcat in the past.. No problems so far with .24 In the past when our apps die with no apparent reason it has been a byte code or deployment problem (usually due to a new JVM).. Rgds, Matt. -Original Message- From: Andi Reinbrech [mailto:[EMAIL PROTECTED] Sent: 14 May 2004 10:31 To: [EMAIL PROTECTED] Subject: Is .24 stable? I have upgraded from .18 to .24 and now my web apps don't work anymore. They just silently terminate in the middle of the process without any exceptions. They come to a point when I instanciate a static member of another class, and the stdout.log appears to be hanging, but in fact it isn't, because I can resubmit the request, and the process will go up to exactly the same place and just die. Any ideas? This still works fine under .18 and when I run the app in test mode - outside of tomcat - hav a dummy class that simulates a web request. Thanks, Andi ** Everything in this e-mail and attachments relating to the official business of MultiChoice Africa is proprietary to the company. Any view or opinion expressed in this message may be the view of the individual and should not automatically be ascribed to the company. If you are not the intended recipient, you may not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and destroy the original message. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: No session in tomcat 5.0.24
Context.xml is great.. But once your WAR has unpacked once, tomcat doesn't overwrite the descriptor in the config/Catalina/hostname/ directory... Rob - I assume you're not using any special session implementation?? -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: 14 May 2004 10:01 To: Tomcat Users List Subject: RE: No session in tomcat 5.0.24 Thats me out of ideas then. Good luck. In tomcat version 4 you could have a context container in your server.xml. In tomcat 5 it is recommended that you have these containers in context.xml in the META-INF directory of each webapp. -Original Message- From: Rob Tillie [mailto:[EMAIL PROTECTED] Sent: 14 May 2004 09:48 To: Tomcat Users List Subject: RE: No session in tomcat 5.0.24 I only uncommented the invoker servlet in the main web.xml, haven't touched the server.xml. But as it works for another app on the same server, I'm guessing this couldn't be the problem? As for context.xml, I have never heard of it, and it isn't present in both webapps. Greetz, -- Rob. -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Friday, May 14, 2004 10:41 AM To: Tomcat Users List Subject: RE: No session in tomcat 5.0.24 What about the main web.xml in the conf directory? and do you have context.xml in the META-INF directory of the app. What about server.xml is that all the same? -Original Message- From: Rob Tillie [mailto:[EMAIL PROTECTED] Sent: 14 May 2004 09:34 To: Tomcat Users List Subject: RE: No session in tomcat 5.0.24 I just did some more investigation. Sessions are working for every app except the most important one :). The web.xml of both apps are empty except for the body of web.xml. Pretty weird, -- Rob. -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Friday, May 14, 2004 10:30 AM To: Tomcat Users List Subject: RE: No session in tomcat 5.0.24 I would hazard a guess that you have made configurational changes to either the server.xml or the web.xml in your older installation. I would look at all the parameters set in these files carefully and see if you can spot a difference. Ta Matt -Original Message- From: Rob Tillie [mailto:[EMAIL PROTECTED] Sent: 14 May 2004 09:06 To: [EMAIL PROTECTED] Subject: No session in tomcat 5.0.24 Hello all, Last night we updated our tomcat server from 5.0.16 to 5.0.24. Suddenly, the web applications don't keep the same session between requests, hereby rendering parts of our applications useless. I have searched the archives but couldn't find any usefull info. Any idea what the problem may be? Greetz, -- Rob. - 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]
First posting + 5.0.19 problem
HI all, this is my first post to this list... I've been using Tomcat for quite some time but only lurked in the archives... However.. I am experiencing a strange problem since upgrading to 5.0.19 and wondered if a resolution has been found. In my log, I see the following error message with no obvious regularity or cause - I'm assuming that it's memory related. I have noticed similar issues mentioned in the archive but have seen no conclusive solution as yet. I believe the problem is related to the JK connector. I am a little unsure which version of JK to use because the website suggests that 1.2.5 is the version to use with Apache1.3 where others strongly recommend JK2... - log extract --- 19-Apr-2004 13:07:11 org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 - log extract --- This only happens with one of my web apps although its context is identical to any of the other 10 we have running. I can submit an identical request ten times and at least one of the requests will abort with the entry above entered in the log. We're running Sun JDK V1.4.2_03 on RedHat Linux 9, Apache 1.3.28, JK 1.2.5, Tomcat 5.0.19 Is the CVS 5.0.21 version stable? perhaps this issue is fixed in the latest version? I scanned the change log but found no obvious mention.. We don't see this error in any version prior to 5.0.19 - I've tested 4.0.3, 4.1.x and 5.0.18 Regards, Matthew.
