[OT] Console when running as a service.

[Leo Donahue - RDSA IT <Le...@mail.maricopa.gov>]

I would be curious to find out how many users run Tomcat from the console in a virtual machine environment.

When you remote into your virtual machine that is running Tomcat from the console, you must not be logging off of that session are you?  How do you keep the console window open, unless you just close the session?  When you remote back into your server after time passes, how do you know you will get the same session?

In our virtual environment, I've never been able to leave the console window running.  Something eventually kills the console window, so we've been running it as a service.

Leo

RE: [OT] Console when running as a service.

["Harris, Jeffrey E." <Je...@ManTech.com>]

> -----Original Message-----
> From: Leo Donahue - RDSA IT [mailto:LeoDonahue@mail.maricopa.gov]
> Sent: Monday, March 11, 2013 10:56 AM
> To: Tomcat Users List (users@tomcat.apache.org)
> Subject: [OT] Console when running as a service.
>
> I would be curious to find out how many users run Tomcat from the
> console in a virtual machine environment.
>
> When you remote into your virtual machine that is running Tomcat from
> the console, you must not be logging off of that session are you?  How
> do you keep the console window open, unless you just close the session?
> When you remote back into your server after time passes, how do you
> know you will get the same session?
>
> In our virtual environment, I've never been able to leave the console
> window running.  Something eventually kills the console window, so
> we've been running it as a service.
>
> Leo
>
We always run Tomcat as a service, but to answer your questions:

If you run Tomcat from a console, you cannot log off; otherwise, the application terminates.

You can disconnect from the session (not log off) and any applications already running keep running.  Normally, you would reconnect to the same session, but if you do not, you can use Terminal Services Manager to reconnect to the session (by default, Windows Server 2000 and 2003 allow two administrator sessions at the same time plus the local console connection; by default, Windows Server 2008 and later normally connect to the console session, although that can be changed by configuring local or domain group policies to allow multiple sessions as in Windows Server 2000 and 2003).

Although the default is that disconnecting a session leaves it running until someone either logs out of the session or reboots the server, many organizations set an idle time limit for disconnected or inactive sessions, and actually reset them after the time limit is reached, which is the same as logging out.

Jeffrey Harris

This e-mail and any attachments are intended only for the use of the addressee(s) named herein and may contain proprietary information. If you are not the intended recipient of this e-mail or believe that you received this email in error, please take immediate action to notify the sender of the apparent error by reply e-mail; permanently delete the e-mail and any attachments from your computer; and do not disseminate, distribute, use, or copy this message and any attachments.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: [OT] Console when running as a service.

[André Warnier <aw...@ice-sa.com>]

Leo Donahue - RDSA IT wrote:
> I would be curious to find out how many users run Tomcat from the console in a virtual machine environment.
> 
> When you remote into your virtual machine that is running Tomcat from the console, you must not be logging off of that session are you?  How do you keep the console window open, unless you just close the session?  When you remote back into your server after time passes, how do you know you will get the same session?
> 
> In our virtual environment, I've never been able to leave the console window running.  Something eventually kills the console window, so we've been running it as a service.
> 

I do this all the time, on a series of servers (Tomcat or others), often on several 
servers at once from my laptop.
Using a vSphere Client or VNC for instance, does not logoff the user session or close any 
window when you connect/disconnect.   It is only MS Remote Desktop or Remote Console 
thingies who do that.

And both the above solutions require a password to connect to the console, so since there 
is no "real" physical console attached to the server, the fact of leaving this console 
"logged-in" is not any more of a security issue than anything else.

I am not advocating this solution as a universal solution to everything. There are cases 
when running as a Windows Service is more appropriate (or mandatory).  In some other 
cases, the above solutions are more practical. YMMV as they say.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org