Jan- BB software has the potential to cause a considerable amount of havoc and heartache you could be damaging the disks if you dont quiesce all of your DB,mail,ftp, tc servers first
I can see the utility to either turn on or turn off smart appliances though.. Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > Date: Mon, 6 Oct 2008 15:22:38 -0600 > From: [EMAIL PROTECTED] > To: users@tomcat.apache.org > Subject: Re: Using tomcat to hold many open connections. > > tomcat has one too, it's called the CometProcessor > > Filip > > Clemens Eisserer wrote: > > Jetty has a special api to allow exactly this kind of request efficiently. > > The thread is not kept assignd to the "sleeping" connection, but is re-used. > > > > lg Clemens > > > > 2008/10/6 Kees Jan Koster <[EMAIL PROTECTED]>: > > > >> Dear Uprooter, > >> > >> > >>> I'm looking for a server that has to hold many (web services) remote > >>> clients > >>> for controlling them. > >>> I want to do things like sending power off command to a bunch of machines > >>> remotely. > >>> > >> Building a botnet? :-) > >> > >> > >>> The clients are usually windows machines behind firewalls NAT or web > >>> proxies that only allow HTTP (this is why I thought of webservices) > >>> > >>> The regular request-response fashion that servlet follows is not suitable > >>> here since the initiator of the operation is the server. > >>> What can I do in order to solve this and still use web services? > >>> > >> If you have the resources, you can just block in the servlet on your > >> server. > >> It's pretty expensive since Tomcat uses a thread per request I believe. > >> Java > >> threads are expensive (256kB each?), so that adds up quickly. You could > >> spend some time tuning your thread stacks, though. Depending on your actual > >> number of clients, you should be able to get this to work with a few GB of > >> RAM. > >> > >> But then, 20K client polling once an hour might be cheaper. You may want to > >> find a way to stagger the requests though. > >> > >> -- > >> Kees Jan > >> > >> http://java-monitor.com/forum/ > >> [EMAIL PROTECTED] > >> 06-51838192 > >> > >> The secret of success lies in the stability of the goal. -- Benjamin > >> Disraeli > >> > >> > >> --------------------------------------------------------------------- > >> To start a new topic, e-mail: users@tomcat.apache.org > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _________________________________________________________________ Get more out of the Web. Learn 10 hidden secrets of Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008
