7.0.4 Parallel deployment, war name invalid
Hi, was trying the parallel deployment feature: - have an app xapp under webapps, running - created a new war of xapp, named xapp##001.war - placed the under webapps no xapp#001 folderlogs says: SEVERE: The war name [xapp##001.war] is invalid. The archive will be ignored. any idea? Gabriele. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Deployment over a running webapp does not call session detroyed?
I was really hoping that the bug was mine, but...in my case, mantaining sessions during deployment is totally useless, because my server classes instances have changed, probably destroyed by Tomcat, and most of them are obviously per session instances. Also, Tomcat seems to destroy jndi data sources during deployment, thus invalidating any previously taken data source. As my webapp is secured through JAAS, I also notice that reloading the webapp after deployment, brings me back to the configured login page, as if the security context is no more valid. So, my question is, what is the point to mantain http sessions valid when all the other stuff have been destroyed and reloaded? If there is any design I should follow to recreate my new object structure on the mantained sessions, I would try to do it. Thanx a lot! Gabriele. -- Da: Caldarale, Charles R A: Tomcat Users List Data: 12 dicembre 2011 19.02.26 CET Oggetto: RE: Deployment over a running webapp does not call session detroyed? From: Gabriele Bulfon [mailto:gbul...@sonicle.com] Subject: Deployment over a running webapp does not call session detroyed? the ContextListener contextDestroyed is called, but I have no way to access my threads and kill them from there Is this a bug or am I missing something? Yes, it's a bug - yours. By design, sessions are maintained across a webapp redeployment. You'll need to make your code smarter about tracking auxiliary threads that you start and that Tomcat is completely unaware of. For example, you could save the threads in some sort of list or array accessible to your context listener, and have it take care of shutting down your threads. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Deployment over a running webapp does not call session detroyed?
Hi, don't know if this is a problem of Tomcat integrated into NetBeans, but I noticed that rebuilding my webapp (causing netbeans redeployment over the running webapp), older threads spawn by running sessions are not killed, getting into exceptions because the real HttpSession objects are killed and the jndi connections are closed. I have a SessionListener in my webapp that kills this threads and cleanly exit the session, but this is never called when redeployed. On the other hand, the ContextListener contextDestroyed is called, but I have no way to access my threads and kill them from there Is this a bug or am I missing something? Gabriele. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 - Firefox - SWF Upload
The conf/context.xml is the default one from Tomcat7 distribution. My webapp context.xml just contains resources definitions such as jdbc pools. Where should I place this useHttpOnly flag, if this is the solution? My real question is about the jsessionid that is stated to be changed on tomcat7, so maybe swfupload is not able to track the session and run correctly. -- Da: Mark Thomas A: Tomcat Users List Data: 7 febbraio 2011 15.49.46 CET Oggetto: Re: Tomcat7 - Firefox - SWF Upload On 07/02/2011 14:13, Gabriele Bulfon wrote: Thanks, I have only this inf conf: conf/Catalina/localhost and it's empty. What is this? That is fine. It is the location optionally copies context.xml files to but Tomcat 7.0.x does not do this by default. What is in conf/context.xml? What is in webapps/ /META-INF/context.xml? Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 - Firefox - SWF Upload
I think I already tried placing that flag in my context.xml where you suggested, but it didn't work I'll try again and let you know. Thanks, Gabriele. -- Da: Mark Thomas A: Tomcat Users List Data: 9 febbraio 2011 12.18.15 CET Oggetto: Re: Tomcat7 - Firefox - SWF Upload On 09/02/2011 09:19, Gabriele Bulfon wrote: The conf/context.xml is the default one from Tomcat7 distribution. My webapp context.xml just contains resources definitions such as jdbc pools. Where should I place this useHttpOnly flag, if this is the solution? In your app's /META-INF/context.xml change ... to ... My real question is about the jsessionid that is stated to be changed on tomcat7, so maybe swfupload is not able to track the session and run correctly. The reason is that the httpOnly attribute of a cookie prevents the cookie from being available to scripts and applets. This prevents the applet reading the session ID. Setting useHttpOnly=false stops the httpOnly flag from being added to the cookie and makes it available to scripts and applets. Be aware that disabling the httpOnly attribute on the cookie significantly increases the impact of any XSS vulnerabilities in your web application. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 - Firefox - SWF Upload
ohps, looks like it's working now :) don't know what I did wrong the previous time...probably I did not restart completely tomcat, but just restarted the webapp? well, solved anyway :) thanks a lot! -- Da: Mark Thomas A: Tomcat Users List Data: 9 febbraio 2011 12.18.15 CET Oggetto: Re: Tomcat7 - Firefox - SWF Upload On 09/02/2011 09:19, Gabriele Bulfon wrote: The conf/context.xml is the default one from Tomcat7 distribution. My webapp context.xml just contains resources definitions such as jdbc pools. Where should I place this useHttpOnly flag, if this is the solution? In your app's /META-INF/context.xml change ... to ... My real question is about the jsessionid that is stated to be changed on tomcat7, so maybe swfupload is not able to track the session and run correctly. The reason is that the httpOnly attribute of a cookie prevents the cookie from being available to scripts and applets. This prevents the applet reading the session ID. Setting useHttpOnly=false stops the httpOnly flag from being added to the cookie and makes it available to scripts and applets. Be aware that disabling the httpOnly attribute on the cookie significantly increases the impact of any XSS vulnerabilities in your web application. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7 - Firefox - SWF Upload
Thanks, I have only this inf conf: conf/Catalina/localhost and it's empty. What is this? Gabriele. -- Da: Pid A: Tomcat Users List Data: 7 febbraio 2011 15.13.26 CET Oggetto: Re: Tomcat7 - Firefox - SWF Upload On 07/02/2011 12:37, Gabriele Bulfon wrote: Sorry, I thought it was an already known issue. I'm using SWFUpload, a mix of javascript/flash that enables multiple files to be uploaded with multiselection. It uses JSESSIONID to mantain session. I have read these two links about the problem: http://forums.alfresco.com/en/viewtopic.php?f=11t;34975 http://issues.alfresco.com/jira/browse/ALF-6850 This last one talks about an useHttpOnly flag in the context.xml. I tried both in my own webapp context.xml and in the global conf/context.xml , but it doesn't fix the problem. Undo the setting in the global conf/context.xml. Check that the updated version in your app META-INF/context.xml is actually copied to conf/Catalina/[hostname]/[appname].xml. p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat web app versioning
Fantastic! This is a feature I asked about on this list some months ago, because Resin already has something similar, and I was answered that this was not in the to do list for Tomcat. Maybe someone has listened to my request? ;) Thanks a lot, this saves me so much from the hassle of updating customers web apps! ;) Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com -- Da: Mark Thomas A: Tomcat Users List Data: 17 gennaio 2011 18.34.40 CET Oggetto: Re: Tomcat web app versioning On 17/01/2011 17:21, Gabriele Bulfon wrote: Hello, I read somewhere that the latest Tomcat 7 is able to handle web app versioning, but I can't find any documentation about it. What is it about? http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Introduction covers the basics. Note versions are treated as strings so ##11 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat web app versioning
Hello, I read somewhere that the latest Tomcat 7 is able to handle web app versioning, but I can't find any documentation about it. What is it about? Thanks Gabriele. -= Mail sent through WebTop2 =- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Login page timeout
Hello, I'm trying to figure out how to solve a very stupid problem. I have a solution, but I want to know if there is some other better ways. I have a webapp configured with jaas security. The login form page is configured and the security check works perfectly. But, if a user starts the browser and goes to the login page, then leaves the browser there for some reason, when he/she gets back later and try to login, it's like the login form has expired, and TomCat fails with the Invalid direct reference to form login page. The only way I've seen so far to avoid this, is to have a javascript function to reload the login form every n seconds if the user does not enter. It's as if TomCat creates a session for the login form, and this session expires. How can I avoid this? Gabriele. -= Mail sent through WebTop2 =- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Login page timeout
Ok, my workaround will be a javascript code to run a timeout and reload the Login page, trying to reset the timeout when the user is typing. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com -= Mail sent through WebTop2 =- -- Da: Pid * A: Tomcat Users List Data: 22 ottobre 2010 15.14.39 CEST Oggetto: Re: Login page timeout It's not an error. p On 22 Oct 2010, at 13:51, Martin Gainty wrote: can you verify this error is corrected with TC 7.0.5? thanks, Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Fri, 22 Oct 2010 05:16:07 -0700 Subject: Re: Login page timeout From: jbritto...@gmail.com To: users@tomcat.apache.org Top result doing google search http://www.mindspill.org/kiwiThread$msgnum=207 See Mark's response bottom of page: https://issues.apache.org/bugzilla/show_bug.cgi?id=3839#c14 On Fri, Oct 22, 2010 at 3:15 AM, Gabriele Bulfon wrote: Hello, I'm trying to figure out how to solve a very stupid problem. I have a solution, but I want to know if there is some other better ways. I have a webapp configured with jaas security. The login form page is configured and the security check works perfectly. But, if a user starts the browser and goes to the login page, then leaves the browser there for some reason, when he/she gets back later and try to login, it's like the login form has expired, and TomCat fails with the Invalid direct reference to form login page. The only way I've seen so far to avoid this, is to have a javascript function to reload the login form every n seconds if the user does not enter. It's as if TomCat creates a session for the login form, and this session expires. How can I avoid this? Gabriele. -= Mail sent through WebTop2 =- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Updating webapps classes
Hi, again on this subjetc, I discovered that Resin has this feature: http://www.caucho.com/resin/admin/deploy.xtp#web-app%20versioning I think this would be a very nice feature of Tomcat, don't you think? Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com -- Da: Christopher Schultz A: Tomcat Users List Data: 9 luglio 2010 3.01.37 CEST Oggetto: Re: Updating webapps classes -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriele, On 7/7/2010 8:11 AM, Gabriele Bulfon wrote: I get back to this discussion beacuse I was brainstorming again on it, and found that the already present class loader may actually be able to do this alone. My thought was: if Tomcat is capable of managing different application contexts under its work folder, and have them run different applications with different class versions inside their classes/lib, probably it may implement automatic application updates by createing different application contexts behind the scene. Uh, what? I see this scenario: - Tomcat is running my webapp - People have sessions on it, and Tomcat has its application context on my webapp - I place new jar files/classes - Tomcat detects, and instead of reloading and invalidating current sessions, it will keep current sessions on the old application context, until they reach 0 sessions - Meanwhile it may create a new application context to run new sessions That's not how it works. How hard would it be to make this true in Tomcat? Probably not too difficult, but the Tomcat team is unlikely to implement this because the spec (at least as of 2.5) is silent on the subject of auto-deployment (other than to mention that the container is free to implement it). Such a system would be quite chaotic in a clustered environment, because some cluster members would update before others, and, depending upon the configuration of the cluster, information sharing and/or member selection could fail and the whole site could become unstable from a user perspective. I highly recommend performing deliberate application updates by bleeding users off of one server and on to another. Is there any other Java WebApp Container capable of doing this? Dunno. You could probably search the web for something like that. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw2dPEACgkQ9CaO5/Lv0PBTXwCgpTZ9b5rEYImtsRV0cGfbKaN+ 4AMAoIjrUIaVDlw+0Xu1c/BJHd5cAjvW =eeFX -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
To JAAS or not to JAAS
Hello, I have a web application written with JAAS authentication, using my own login modules. This is fine as long as the deployment is made by a system administrator who knows how to configure jaas.config and to place needed jars in the tomcat lib directory, following my instructions. Also, JAAS mode requires the sysadmin to prepare the backend db himself with a sql file of mine, and configure the context.xml with db informations. Now, I would like the same web app to be deployable in 2 ways, both with JAAS and without JAAS, to simplify deployment by less experienced deployer who will just put the war file inside webapp and access the application. During the first access I would like the application to understand that is not working in JAAS mode, check for a properties file inside the webapp, that when not existsant will trigger an installation sequence via web (to configure db access and so on). This will create this properties file that will be the reference configuration, substituting the context.xml / jaas config. My simple idea would be to have this war without the context.xml definitions, then have an init parameter of the application in web.xml to define Use Jaas = Yes/No that will let the webapp understand and do what I described. My question is: do I have a cleaner way to do this? Maybe I have some way to understand that my webapp is under JAAS control or not during application startup? Thanks for any help, Gabriele. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Updating webapps classes
Hello, thx for your answers. I understand your points, but in a non cluster situation, updating the application is a pain, because I'm forced to ask people to exit, update and restart. It may be a possible option to do what I said, and would be my responsability to know if an update may lead to problems because of possible concurrent usage of old and new version. What do you think? Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com -= Mail sent through WebTop2 =- -- Da: Christopher Schultz A: Tomcat Users List Data: 9 luglio 2010 3.01.37 CEST Oggetto: Re: Updating webapps classes -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriele, On 7/7/2010 8:11 AM, Gabriele Bulfon wrote: I get back to this discussion beacuse I was brainstorming again on it, and found that the already present class loader may actually be able to do this alone. My thought was: if Tomcat is capable of managing different application contexts under its work folder, and have them run different applications with different class versions inside their classes/lib, probably it may implement automatic application updates by createing different application contexts behind the scene. Uh, what? I see this scenario: - Tomcat is running my webapp - People have sessions on it, and Tomcat has its application context on my webapp - I place new jar files/classes - Tomcat detects, and instead of reloading and invalidating current sessions, it will keep current sessions on the old application context, until they reach 0 sessions - Meanwhile it may create a new application context to run new sessions That's not how it works. How hard would it be to make this true in Tomcat? Probably not too difficult, but the Tomcat team is unlikely to implement this because the spec (at least as of 2.5) is silent on the subject of auto-deployment (other than to mention that the container is free to implement it). Such a system would be quite chaotic in a clustered environment, because some cluster members would update before others, and, depending upon the configuration of the cluster, information sharing and/or member selection could fail and the whole site could become unstable from a user perspective. I highly recommend performing deliberate application updates by bleeding users off of one server and on to another. Is there any other Java WebApp Container capable of doing this? Dunno. You could probably search the web for something like that. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw2dPEACgkQ9CaO5/Lv0PBTXwCgpTZ9b5rEYImtsRV0cGfbKaN+ 4AMAoIjrUIaVDlw+0Xu1c/BJHd5cAjvW =eeFX -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Updating webapps classes
I get back to this discussion beacuse I was brainstorming again on it, and found that the already present class loader may actually be able to do this alone. My thought was: if Tomcat is capable of managing different application contexts under its work folder, and have them run different applications with different class versions inside their classes/lib, probably it may implement automatic application updates by createing different application contexts behind the scene. I see this scenario: - Tomcat is running my webapp - People have sessions on it, and Tomcat has its application context on my webapp - I place new jar files/classes - Tomcat detects, and instead of reloading and invalidating current sessions, it will keep current sessions on the old application context, until they reach 0 sessions - Meanwhile it may create a new application context to run new sessions How hard would it be to make this true in Tomcat? Is there any other Java WebApp Container capable of doing this? Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com -- Da: Christopher Schultz A: Tomcat Users List Data: 3 maggio 2010 15.57.57 CEST Oggetto: Re: Updating webapps classes -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter, On 4/30/2010 10:33 AM, Peter Crowther wrote: In normal use, Tomcat1 is running. The load balancer directs all users to Tomcat1. Tomcat2 could even be stopped. I would say that normal use would include both (or however many) instances running in parallel. When it's time to upgrade, you mark one or more nodes in the cluster as don't send any new users to this node and wait for all the users on those nodes to complete their work. After that, Peter's scenario is exactly the same. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkve1mUACgkQ9CaO5/Lv0PAOhgCfRCZLdT0flr3es5Oc5IpCCNNl bokAn1F22eum4C6vhHoEv2LjQXee/9uk =IpQb -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Updating webapps classes
Hi, thanx for the interesting solution. Anyway, not always possible to run 2 tomcat instances because of memory requirements. Do you see any different solution with 1 tomcat only (or tomcat + apache)? Thx in advance, Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com -- Da: Peter Crowther A: Tomcat Users List Data: 30 aprile 2010 16.33.39 CEST Oggetto: Re: Updating webapps classes It's very hard to do this using one Tomcat instance. It's very easy to do this using two Tomcat instances (call them Tomcat1 and Tomcat2) and a load balancer (Apache httpd should be fine for this job). In normal use, Tomcat1 is running. The load balancer directs all users to Tomcat1. Tomcat2 could even be stopped. To upgrade, you upgrade Tomcat2 (and start it if needed) and tell the load balancer that new sessions should be sent to Tomcat2. Once all user sessions are off Tomcat1, you upgrade it and tell the load balancer to direct new sessions to Tomcat1. Once all user sessions are off Tomcat2, you can shut it down again or leave it running for fault tolerance. If you have enough RAM on your server (and the load is low enough), you could even run all three of Tomcat1, Tomcat2 and httpd on the same server. Does this help? - Peter On 30 April 2010 14:46, Gabriele Bulfon wrote: Hello, I don't know if I'm asking something stupid, but I'm investigating this for days, and found nothing around. Updating a java webapp can be a problem when this java webapp is being ised 24/7 by users, and many of them have sessions running for all the working hours. Consider that this webapp consists of many instance classes being created during session startup. How can I manage updates of the webapp classes without having to reload the webapp? What I would like is that users inside the application to continue to see the old version, while new ones logging in would see the latest one. I don't know if there is any way for this Thanks Gabriele. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Updating webapps classes
Hello, I don't know if I'm asking something stupid, but I'm investigating this for days, and found nothing around. Updating a java webapp can be a problem when this java webapp is being ised 24/7 by users, and many of them have sessions running for all the working hours. Consider that this webapp consists of many instance classes being created during session startup. How can I manage updates of the webapp classes without having to reload the webapp? What I would like is that users inside the application to continue to see the old version, while new ones logging in would see the latest one. I don't know if there is any way for this Thanks Gabriele. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
