Re: Can't connect to X11
Hi, do you use some graphic functions in your project? If so, you should add the following parameter to Tomcat startup: -Djava.awt.headless=true cu cm Am 22.09.2005 um 09:07 schrieb Iin Nurhidayat: Hi All, I found this error : java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable. on UNIX platform. Please adv. Thanks Regards - IN - PGP.sig Description: Signierter Teil der Nachricht
Howto deploy a new version of my webapp without disturbing the customer?
Hello! My scenario is an order application, where my customers can order products. But the software or the design of the pages are changing rapidly. The question is now: how can I deploy a new version without the customer noticing anything? I'm searching for something similar to what WebObjects is offering. WO allows me to start a new instance (using the new version) of my application in parallel to the already running application. All new connections are then redirected to this new application. The existing sessions in the old application can continue their order process. When the number of open sessions in this old instance reaches zero, the instance is shut down. The customer out in the web does not see that a new version has been deployed. Is something simlilar possible using Tomcat? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Howto deploy a new version of my webapp without disturbing the customer?
Am 01.10.2004 um 14:10 schrieb Andoni: Surely the think that WO is doing is maintaining all sessions on the old machine until they are shut down. Yes, that's what WO is doing. You can see it in the Monitor application. Sessions are bound to the application instance. Otherwise changing the way your sessions are do work would be a dangerous job. My way of doing this is simply to get up at 3:30am and make the changes then! I am lucky in that 90% of my users are 9-5 office workers. You are really lucky not to offer your service to thousands of customers. From what I can see in the sales figures, those customers never sleep! And so do the product managers: the best downtime is no downtime :-) Thus I want to keep the version cycle as small as possible. Christian Andoni. - Original Message - From: Ralph Einfeldt [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, October 01, 2004 12:09 PM Subject: RE: Howto deploy a new version of my webapp without disturbing the customer? Just a guess: - Use Apache + mod_jk(2) + 2 tomcat instances - Use sticky sessions (look at the jvmRoute of the engine tag) - Use the load factor to distribute 100% of the requests to the first instance. - Update the second instance. - Change the load factor to distribute 100% of the requests to the second instance. - Wait after all session moved to the second instance update the first instance and reverse the I haven't tried any of this but as far as I can remember I have seen posts in this list that indicate that this should be possible. -Original Message- From: Christian Mittendorf [mailto:[EMAIL PROTECTED] Sent: Friday, October 01, 2004 12:15 PM To: [EMAIL PROTECTED] Subject: Howto deploy a new version of my webapp without disturbing the customer? Hello! My scenario is an order application, where my customers can order products. But the software or the design of the pages are changing rapidly. The question is now: how can I deploy a new version without the customer noticing anything? I'm searching for something similar to what WebObjects is offering. WO allows me to start a new instance (using the new version) of my application in parallel to the already running application. All new connections are then redirected to this new application. The existing sessions in the old application can continue their order process. When the number of open sessions in this old instance reaches zero, the instance is shut down. The customer out in the web does not see that a new version has been deployed. Is something simlilar possible using Tomcat? Christian - 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]
Re: Howto deploy a new version of my webapp without disturbing the customer?
Hello! It would be really great if we could work out a solution that does the job like the WebObjects Monitor application. Perhaps some kind of howto documentation giving you a step-by-step guide to the setup and usage. There seems to be no Wiki for the Tomcat project page. Is there a tomcat wiki where we could collect information? Christian P.S. Where can I find more information about the balancer? Am 01.10.2004 um 14:52 schrieb Shapira, Yoav: Hi, You are really lucky not to offer your service to thousands of customers. From what I can see in the sales figures, those customers never sleep! And so do the product managers: the best downtime is no downtime :-) Thus I want to keep the version cycle as small as possible. Yes, it's true that customers/users never sleep. I want to offer an alternative approach here. This scenario is one that I had in mind when contributing the balancer app to Tomcat. Using the balancer app to address this issue can result in zero down time. Here's the setup: Initial: - Tomcat server 1 with your app v1.0 - Tomcat server 2 with your app v1.0 turned off - Tomcat front-end running only balancer (so this is a tiny, fast, Tomcat installation consuming almost no resources), which redirects requests for your app to Tomcat server 1. Now v1.1 of your app is ready, here's what you do: - Turn on Tomcat server 2, which has your app v1.0 still - Modify the balancer rules to redirect requests for your app to Tomcat server 2 - Update server 1 (you can turn if off, restart it, do whatever you need, as your users aren't using it now) with your app v1.1 - When it's ready, modify the balancer rules again to that requests for your app go to Tomcat server 1. - Watch things for a while, and if something goes bad with your new app you can just modify the balancer rules so that users go back to 1.0 (again, no down time!) - But if things go well, you can turn off and update server 2 as well so that you're ready for the next round. This is just the standard cluster/traffic-director setup done with Tomcat's balancer, which makes is a 100% Java, 100% free, lightweight solution. There are non-Java and/or $$$ alternatives to this same approach that also work well. The focus is on using multiple servers instead of one, thereby allowing you to modify any one server at a time without causing down time for your users. 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: Howto deploy a new version of my webapp without disturbing the customer?
Am 01.10.2004 um 16:45 schrieb Shapira, Yoav: There seems to be no Wiki for the Tomcat project page. Is there a tomcat wiki where we could collect information? http://wiki.apache.org/jakarta/TomcatProjectPages Thanks, though it does look quite confusing on the first view. It seems as if there is not much content yet related to tomcat. P.S. Where can I find more information about the balancer? In the Tomcat docs there's one devoted to Balancer. It's not a complex webapp, so look at the code as well. Thanks again, I'll have a look at it too. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Preparing to do session sharing
On 13.05.2004, at 08:21, Randy wrote: 1) is it stable? I have seen lots of email traffic and some comments about The only thing worse than dealing with connectors is Clustering I cannot tell you yet if it's stable because the site is not in production yet. First tests have shown some problems, but I think we have nailed them down now to be bugs in the application itself and not in tomcat. We were using references to the objects that we stored in the session and did the changes on these references. That was working nice - but it showed to cause problems and the changed object was not always distributed to all conneced servers. We are now changing our code to use the set... method after changes and it seems to work better. Though we haven't done many tests yet. 1a) do people have this working successfully in a high traffic production env? See my comments on the first point. 2) I am going to use Using in-memory-replication, using the SimpleTcpCluster that ships with Tomcat 5 method Yepp, that's also the way we use in our environment. Would be great if we can help each other on this issue. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to set the JSESSION cookie domain?
Hello all, I'm working on a tomcat project that shall be deployed on multiple hosts. However, we are currently stuck with two problems / questions: 1) How can I specifiy the domain name that tomcat is using for the JSESSIONID cookie? By default tomcat is using the domain name from the request. For example a request to http://www.foo.com will create a JSESSIONID cookie for the domain www.foo.com. But instead we would like the cookie domain to be .foo.com. How can I tell tomcat to use my specified domain name instead of the default behaviour? 2) Problem two is related to session clustering. We are using Tomcat 5 for deployment. A simple example is working nice. However, the complete application is showing some strange behaviour. Sometimes the changed session object is available on every host, sometimes not. Is there a way to make the session mechanism more verbose? Can we instruct Tomcat to tell us whenever he is changing objects in the session store between different hosts? Where can we find some detailed information about this topic? Thanks for your help! Greetings Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mac OSX
On Dienstag, Juli 9, 2002, at 01:31 Uhr, Martin Jacobson wrote: Matt Preston wrote: In the end the only way that I could get Tomcat to start up was to copy all of the jars (common/lib server/lib bootstrap.jar) into /System/Framework/Java/Extensions [...] The only stuff I have in the standard extensions is some security encryption stuff - eq JSEE. In the case of local Java extensions on Mac OS X I think /Library/Java/Extensions is the better solution. cu cm -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
