tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51587] Implement status and uptime commands
Date Tue, 02 Aug 2011 07:53:04 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51587

--- Comment #2 from Konstantin Kolinko <knst.kolinko@gmail.com> 2011-08-02 07:53:04
UTC ---
(In reply to comment #1)
> I'm not sure why you'd use a non-daemon waiting loop, instead of a simple
> single-threaded daemon listener.

That there should always be a non-daemon Thread in a JVM, because that is what
keeps JVM alive. Currently this task is performed by Main thread that loops
inside StandardServer.await().

I thought that maybe this task can be performed by the listener as well, and
let the Main thread just exit without waiting.

Maybe it is over-engineering though and these tasks could be separate.

> There is no need for a "shutdown" command on this port IMO.

Look at Catalina.stopServer(String[]) and createStopDigester() that it calls.
The support for new command, Catalina.status(..), could be implemented in the
same place. It is easier to read port number from <Server> element like
createStopDigester() does than trying to figure what Listeners are configured.
Thus it is the same port.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


Mime
View raw message