You can use "netstat -a" to see if the Tomcat port number is listening.
On Sat, Nov 14, 2009 at 4:09 PM, SRamasamy wrote:
>
> >>That's bad; each time the user clicks the link a new instance of Tomcat
> will start, all but the first of which will die due to port conflicts.
> Sloppy, at best. Yo
>>That's bad; each time the user clicks the link a new instance of Tomcat
will start, all but the first of which will die due to port conflicts.
Sloppy, at best. You should have the links target your own script that
determines whether or not Tomcat is running and starts it only when needed.
--
E
> From: Ziggy [mailto:zigg...@gmail.com]
> Subject: Re: Tomcat really need Shutdown port
>
> If you dont configure the shutdown port how will tomcat know
> which instance to shutdown if you have configured mulitple
> tomcat instances using multiple catalina_bases??
If you don
a [mailto:su...@techie.com]
> > Subject: RE: Tomcat really need Shutdown port
> >
> > As of my knowledge and other tomcat related document and experts
> > response it’s states we need tomcat port need to shuts down for
> > windows.
>
> Read all the responses; you do *not*
> From: SRama [mailto:su...@techie.com]
> Subject: RE: Tomcat really need Shutdown port
>
> As of my knowledge and other tomcat related document and experts
> response it’s states we need tomcat port need to shuts down for
> windows.
Read all the responses; you do *not* need th
Dear Guys,
As of my knowledge and other tomcat related document and experts response
it’s states we need tomcat port need to shuts down for windows.
I have one more clarification regarding tomcat port
Over view of my product: our product based developed by struts web
application its running on
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Bill Barker
> Subject: Re: Tomcat really need Shutdown port
>
> On Windows, you need the shutdown port (so that anybody with physical
> access to the machine can shutdown the service by using the scripts).
The above seems to co
"Mark Thomas" wrote in message
news:4afdf745.6000...@apache.org...
> Caldarale, Charles R wrote:
>>> From: Mark Thomas [mailto:ma...@apache.org]
>>> Subject: Re: Tomcat really need Shutdown port
>>>
>>> If you set the shutdown port to -1 then the
> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: Tomcat really need Shutdown port
>
> CTRL-C if running in a console.
I verified that CTRL-C does a clean shutdown. Terminating via Task Manager or
the close button on the command window causes abrupt termination, not a
Caldarale, Charles R wrote:
>> From: Mark Thomas [mailto:ma...@apache.org]
>> Subject: Re: Tomcat really need Shutdown port
>>
>> If you set the shutdown port to -1 then the standard process
>> kill (ie kill -15 on linux) will perform a standard,
>> perfectly
On 13/11/2009 22:27, Caldarale, Charles R wrote:
From: Mark Thomas [mailto:ma...@apache.org]
Subject: Re: Tomcat really need Shutdown port
If you set the shutdown port to -1 then the standard process
kill (ie kill -15 on linux) will perform a standard,
perfectly safe shutdown identical to what
> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: Tomcat really need Shutdown port
>
> If you set the shutdown port to -1 then the standard process
> kill (ie kill -15 on linux) will perform a standard,
> perfectly safe shutdown identical to what you would get
Caldarale, Charles R wrote:
>> From: SRamasamy [mailto:su...@techie.com]
>> Subject: Tomcat really need Shutdown port
>>
>> I have removed port but its working. let me know how its working after
>> removing shutdonw port ?
>
> Without the shutdown port, you will not be able to stop Tomcat via the
> From: SRamasamy [mailto:su...@techie.com]
> Subject: Tomcat really need Shutdown port
>
> I have removed port but its working. let me know how its working after
> removing shutdonw port ?
Without the shutdown port, you will not be able to stop Tomcat via the normal
scripts. You can terminate
14 matches
Mail list logo
