Hello Peter,
> -Ursprüngliche Nachricht-
> Von: l...@kreuser.name
> Gesendet: Donnerstag, 11. Mai 2023 16:16
> An: Tomcat Users List
> Betreff: Re: Java Agent and Tomcat shutdown
>
> Hi Thomas
>
> > Am 11.05.2023 um 16:05 schrieb Thomas Hoffmann (Speed
Hi Thomas
> Am 11.05.2023 um 16:05 schrieb Thomas Hoffmann (Speed4Trade GmbH)
> :
>
> Hello,
>
> we are using a java agent to start a listening process (JMX proxy).
>
> The systemd file for tomcat looks like (snippet):
> JAVA_OPTS=... -javaagent:/opt/runtime/jmxagent/jmxagent.jar
> -Dorg.gokt
Hello,
we are using a java agent to start a listening process (JMX proxy).
The systemd file for tomcat looks like (snippet):
JAVA_OPTS=... -javaagent:/opt/runtime/jmxagent/jmxagent.jar
-Dorg.goktay.rmiregistry.port=15000 -Dorg.goktay.rmiserver.port=15001
ExecStart=/opt/apache-tomcat/bin/cata
íguez Fernández
Sent: Monday, June 8, 2020 3:42 AM
To: Tomcat Users List
Subject: [EXTERNAL] Re: Ensuring clean Tomcat shutdown
Hello Amit,
Well, your approach will work. Personally, I do not like very much to parse
logs. We, for instance, in our tomcat instances we provide an application th
rencesThreads The
> web application [AAA] appears to have started a thread named [BBB] but has
> failed to stop it. This is very likely to create a memory leak. Stack trace
> of thread:"
>
> I wanted to ensure a clean Tomcat shutdown and thinking of an automated
> test:
>
ailed
to stop it. This is very likely to create a memory leak. Stack trace of thread:"
I wanted to ensure a clean Tomcat shutdown and thinking of an automated test:
1. Stop Tomcat
2. Parse/grep Catalina logs for warnings like above
3. If found, fail the test, if not pass
Is ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roger,
On 5/9/20 20:45, Roger Marquis wrote:
> calder wrote:
>> We've never had occasion to use the password, because we disable
>> shutdown (the better option).
>
> Never did understand this Tomcat oddity. What other application
> is configured by
вс, 10 мая 2020 г. в 22:20, Mark Thomas :
>
> On May 10, 2020 11:31:02 AM UTC, calder wrote:
>
>
>
> >I asked the DevOps person about the error - turns out it was a
> >SAXParseException when using the & char in the string.
>
> That is standard XML. You have to escape reserved characters in the XM
On May 10, 2020 11:31:02 AM UTC, calder wrote:
>I asked the DevOps person about the error - turns out it was a
>SAXParseException when using the & char in the string.
That is standard XML. You have to escape resevered characters in the XML.
> He vaguely
>remembers a shell issue with the bang
On Sat, May 9, 2020 at 5:09 PM Christopher Schultz
wrote:
> On 5/9/20 00:36, calder wrote:
> > On Fri, May 8, 2020 at 9:07 PM calder
[snip]
> > Keep in mind - some characters won't work like & or ( or ) - at
> > least on Unix-style OSes as the shell may want to interpret them.
>
> What makes you
calder wrote:
We've never had occasion to use the password, because we disable shutdown
(the better option).
Never did understand this Tomcat oddity. What other application is
configured by default to open a tcp socket just to receive a shutdown
command? Then there the default password, both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Calder,
On 5/9/20 00:36, calder wrote:
> On Fri, May 8, 2020 at 9:07 PM calder
> wrote:
>>
>> On Fri, May 8, 2020, 19:20 Robert Hicks
>> wrote:
>>>
>>> I am trying to find what the password complexity can be. I've
>>> looked at several hardening g
On Fri, May 8, 2020 at 9:07 PM calder wrote:
>
> On Fri, May 8, 2020, 19:20 Robert Hicks wrote:
>>
>> I am trying to find what the password complexity can be. I've looked at
>> several hardening guides and they are all "WordsLikeThis". Does the
>> shutdown password take symbols and numbers or at
On Fri, May 8, 2020, 19:20 Robert Hicks wrote:
> I am trying to find what the password complexity can be. I've looked at
> several hardening guides and they are all "WordsLikeThis". Does the
> shutdown password take symbols and numbers or at least hyphenated words?
>
We've never had occasion to
I am trying to find what the password complexity can be. I've looked at
several hardening guides and they are all "WordsLikeThis". Does the
shutdown password take symbols and numbers or at least hyphenated words?
Thanks,
Bob
Thanks for the info. I'll investigate further into the listeners.
On Sat, Mar 17, 2018 at 4:27 AM, Mark Thomas wrote:
> On 16/03/18 22:42, Alex O'Ree wrote:
> > I have a war file that defines a context.xml file, some cxf based web
> > services and a few other background tasks using quartz that a
On 16/03/18 22:42, Alex O'Ree wrote:
> I have a war file that defines a context.xml file, some cxf based web
> services and a few other background tasks using quartz that are initialized
> in a servlet context listener.
>
> When tomcat shuts down, it appears that tomcat stops the database
> connec
I have a war file that defines a context.xml file, some cxf based web
services and a few other background tasks using quartz that are initialized
in a servlet context listener.
When tomcat shuts down, it appears that tomcat stops the database
connection pool before the cxf services or the quartz t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amit,
On 9/17/16 9:41 AM, Amit Pande wrote:
> This might not be the right forum to ask this question. Yet wanted
> to if anyone faced this issue.
>
> Our application uses Jacorb library to talk to legacy daemons over
> CORBA.
>
> However while st
This might not be the right forum to ask this question. Yet wanted to if
anyone faced this issue.
Our application uses Jacorb library to talk to legacy daemons over CORBA.
However while stopping the Tomcat, observing following errors. They are from
the jacrob.jar ..but not sure how to prevent
I'm receiving the following errors when shutting down tomcat7 and it may be a
clue to my software that runs on tomcat. Any suggestions? Thanks in advance,
Aug 24, 2016 12:34:12 PM org.apache.catalina.startup.Catalina stopServer
SEVERE: Could not contact localhost:8005. Tomcat may not be runn
On 05/04/2016 21:48, Vinicius Carvalho wrote:
> Thanks for the quick reply Mark, one final question, does tomcat return a
> 503 error in that case?
New connections will fail. Existing connections will be closed.
Mark
>
> Regards
>
> On Tue, Apr 5, 2016 at 4:05 PM, Mark Thomas wrote:
>
>> On
Thanks for the quick reply Mark, one final question, does tomcat return a
503 error in that case?
Regards
On Tue, Apr 5, 2016 at 4:05 PM, Mark Thomas wrote:
> On 05/04/2016 20:54, Vinicius Carvalho wrote:
> > Hi there, I googled this one around, but I found a big mix on exactly how
> > tomcat o
On 05/04/2016 20:54, Vinicius Carvalho wrote:
> Hi there, I googled this one around, but I found a big mix on exactly how
> tomcat operates when a shutdown is initiated. What happens when a shutdown
> is started in regards to:
>
> - Requests that are currently being processed (if a request is wait
Hi there, I googled this one around, but I found a big mix on exactly how
tomcat operates when a shutdown is initiated. What happens when a shutdown
is started in regards to:
- Requests that are currently being processed (if a request is waiting on
an external resource such as a jdbc connection),
Hello,
I am having an issue with Tomcat shutdown. Requests arriving while the
servlet container is shutting down seem to be held up by the connector
until container shutdown finishes. The shutdown sequence appears to be: (1)
pause connectors, (2) stop containers, (3) stop connectors. I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vimal,
On 8/9/13 1:01 AM, Vimal Jain wrote:
> I am using tomcat-6 on my Ubuntu 13.10 desktop. My question is :-
> When i run shutdown script of tomcat , does tomcat wait for
> currently running threads to complete before shutting down ?
Do you mean
Hi,
I am using tomcat-6 on my Ubuntu 13.10 desktop.
My question is :- When i run shutdown script of tomcat , does tomcat wait
for currently running threads to complete before shutting down ?
--
Thanks and Regards,
Vimal Jain
On 5/20/2013 2:45 PM, Nick Williams wrote:
On May 20, 2013, at 4:39 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Has
On May 20, 2013, at 4:39 PM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/20/13 4:10 PM, Nick Williams wrote:
>>
>> On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> Nick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 4:10 PM, Nick Williams wrote:
>
> On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Nick,
>>
>> On 5/20/13 12:48 PM, Nick Williams wrote:
>>>
>>> On May 20, 2013,
On May 20, 2013, at 2:59 PM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/20/13 12:48 PM, Nick Williams wrote:
>>
>> On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> Ni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/20/13 12:48 PM, Nick Williams wrote:
>
> On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Nick,
>>
>> On 5/19/13 11:25 AM, Nick Williams wrote:
>>> Unfortunately, requ
On May 20, 2013, at 10:56 AM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/19/13 11:25 AM, Nick Williams wrote:
>> Unfortunately, requiring users to call System.gc() before shutdown
>> for logging to work properly is no better than requiring
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/19/13 11:25 AM, Nick Williams wrote:
> Unfortunately, requiring users to call System.gc() before shutdown
> for logging to work properly is no better than requiring users to
> register a listener in a web application for logging to work
>
2013/5/19 Nick Williams :
>
> On May 19, 2013, at 10:01 AM, Caldarale, Charles R wrote:
>
>>> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
>>> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat
>>> shutdown (memory leak, it looks
On May 19, 2013, at 10:01 AM, Caldarale, Charles R wrote:
>> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
>> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat shutdown
>> (memory leak, it looks like)
>
>> Log4j 1 never required a list
> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat shutdown
> (memory leak, it looks like)
> Log4j 1 never required a listener to be configured to be shut down
> properly when an application is un
On May 19, 2013, at 3:33 AM, Mark Thomas wrote:
> On 19/05/2013 05:57, Nick Williams wrote:
>> Can one of the very knowledgeable developers that have been
>> discussing memory leaks in the last few days (re: Possible
>> false-postive with JreMemoryLeakPreventionListener and Tomcat's JDBC
>> Pool
On 19/05/2013 05:57, Nick Williams wrote:
> Can one of the very knowledgeable developers that have been
> discussing memory leaks in the last few days (re: Possible
> false-postive with JreMemoryLeakPreventionListener and Tomcat's JDBC
> Pool and OracleTimeoutPollingThread) chime in on this Log4j 2
Can one of the very knowledgeable developers that have been discussing memory
leaks in the last few days (re: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread) chime in on this Log4j 2 bug [1]?
Log4j 2 appears to be registering a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 8/14/12 3:20 PM, Caldarale, Charles R wrote:
>> From: Davis, Chad [mailto:chad.da...@emc.com] Subject: RE: tomcat
>> shutdown clarification
>
>> And how does the -force option affect this? Will that kill t
> From: Davis, Chad [mailto:chad.da...@emc.com]
> Subject: RE: tomcat shutdown clarification
> And how does the -force option affect this? Will that kill the
> JVM regardless . . .
Usually. The -force option will invoke kill -9 on the Tomcat pid if Tomcat
doesn't stop in t
> > When I use the shutdown.sh script to stop tomcat, what happens?
>
> I am tempted to say "Magic."
That's good ;)
>
> > BUT the JVM won't go down if there are still other threads running
>
> > Am I missing anything important?
>
> Just one point: if the other threads are daemon threads, th
> From: Davis, Chad [mailto:chad.da...@emc.com]
> Subject: tomcat shutdown clarification
> When I use the shutdown.sh script to stop tomcat, what happens?
I am tempted to say "Magic."
> BUT the JVM won't go down if there are still other threads running
> Am I mis
When I use the shutdown.sh script to stop tomcat, what happens?
My understanding is as follows, please correct where wrong.
Each of the Servlet Context's, aka web apps, will have their stop lifecycle
methods invoked. Tomcat itself will stop it's own mechanisms, such as port
listeners, etc.
Thanks Chuck. Will try that. Appreciate your help.
On Fri, Jan 6, 2012 at 4:51 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Kamal Sheikh [mailto:kama...@gmail.com]
> > Subject: Re: Tomcat Shutdown
>
> > I'm pasting some informatio
> From: Kamal Sheikh [mailto:kama...@gmail.com]
> Subject: Re: Tomcat Shutdown
> I'm pasting some information from the logs:
> # A fatal error has been detected by the Java Runtime Environment:
> # Internal Error (safepoint.cpp:247), pid=306, tid=140562856904448
> # g
Thanks for the reply. I'm pasting some information from the logs:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (safepoint.cpp:247), pid=306, tid=140562856904448
# guarantee(PageArmed == 0) failed: invariant
#
# JRE version: 6.0_20-b20
# Java VM: OpenJD
2012/1/7 Kamal Sheikh :
> Hi, I'm new to this but please direct me if I'm posting to the wrong list.
>
> Our Tomcat has suddenly stopped working this morning and now wouldn't start
> -- it responds simply by saying: "failed".
What is in the logs?
Maybe there is no free space on the harddrive?
Ma
Hi, I'm new to this but please direct me if I'm posting to the wrong list.
Our Tomcat has suddenly stopped working this morning and now wouldn't start
-- it responds simply by saying: "failed".
Is there anything going on with OpenJDK and Tomcat?
Here's our configuration:
Java:
java version "1
On 10.06.2011 16:55, Caldarale, Charles R wrote:
>> From: April Easton [mailto:aeas...@shawneecourt.org]
>> Subject: Tomcat shutdown issues
>
>> I don't see any of my threads in there
>
> Look harder:
>
>> "Worker-JM" prio=3D10 t
Taking out what I did for the YourKit plug-in didn't help. Next, I shutdown my
Eclipse and then started and stopped Tomcat on the server. The org.eclipse
threads were still listed in the thread dump. I recently upgraded B.I.R.T. to
version 2.2 on Tomcat and it uses osgi jar files. I'll look
I just installed a plug-in to try and get YourKit going to find the leaks. I
didn't realize that I had started Tomcat from inside Eclipse. I'll take out
what I did.
Thanks,
April
-
To unsubscribe, e-mail: users-unsubscr...@to
> From: April Easton [mailto:aeas...@shawneecourt.org]
> Subject: Tomcat shutdown issues
> I don't see any of my threads in there
Look harder:
> "Worker-JM" prio=3D10 tid=3D0x5d7a1800 nid=3D0x521f in Object.wait()
> at
> org.eclipse.core
On 10/06/2011 15:36, April Easton wrote:
> Good day,
> I've been working on closing all my threads in my applications that run
> on Tomcat. I recently upgraded to 7.0.14 to get better messages concerning
> why Tomcat wasn't shutting down properly. I have stopped all my servlets and
> thre
Good day,
I've been working on closing all my threads in my applications that run on
Tomcat. I recently upgraded to 7.0.14 to get better messages concerning why
Tomcat wasn't shutting down properly. I have stopped all my servlets and
threads, but I'm still having trouble. Below is the th
On 3/1/2011 3:54 PM, Caldarale, Charles R wrote:
Anything using an org.apache class is Tomcat-specific, and
> therefore not portable.
Oh, right. I had not picked up that LifecycleListener itself is
a Catalina class.
Still, the basic issue is not about the listener per se but how
the app server
> From: Olivier Lefevre [mailto:lefev...@yahoo.com]
> Subject: Re: Getting the Tomcat shutdown port
> Just to be 100% clear, this is a Tomcat thing, not a servlet
> spec thing, right? Just wondering whether it's portable.
Anything using an org.apache class is Tomcat-specific,
On 01/03/2011 14:46, Olivier Lefevre wrote:
> On 3/1/2011 2:57 PM, Mark Thomas wrote:
>> Providing you throw an Error, Tomcat is guaranteed not to start.
>
> OK! Just to be 100% clear, this is a Tomcat thing, not a servlet
> spec thing, right? Just wondering whether it's portable.
Yes, this is To
On 3/1/2011 2:57 PM, Mark Thomas wrote:
Providing you throw an Error, Tomcat is guaranteed not to start.
OK! Just to be 100% clear, this is a Tomcat thing, not a servlet
spec thing, right? Just wondering whether it's portable.
-- O.L.
On 01/03/2011 13:52, Olivier Lefevre wrote:
> On 2/28/2011 8:18 PM, Mark Thomas wrote:
>> http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/security/SecurityListener.java?view=annotate
>>
>
> This is brand new, isn't it? I can't find it in the 7.0.8 sources.
Yes.
> So it may thro
On 2/28/2011 8:18 PM, Mark Thomas wrote:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/security/SecurityListener.java?view=annotate
This is brand new, isn't it? I can't find it in the 7.0.8 sources.
So it may throw a java.lang.Error at Lifecycle.BEFORE_INIT_EVENT
time but
On 2/28/2011 6:09 PM, Caldarale, Charles R wrote:
The servlet, or the webapp?
The webapp in this case: the servlet that might fail is the
"worker" servlet, the others more in a supporting role (e.g.,
UI). So if it fails the whole webapp should shut down.
Why don't you simply throw a ServletEx
On 28/02/2011 19:13, Olivier Lefevre wrote:
> I know it's an interface I have to implement but without some
> concrete class "close" to my problem to look at for guidance
> LifecycleListener in and of itself does not help me much.
Ah, OK. Try this:
http://svn.apache.org/viewvc/tomcat/trunk/java/o
On 2/28/2011 6:06 PM, Mark Thomas wrote:
If you want to stop a single Servlet then Servlet.init() is the
place to it. See section 2.3.2 of the Servlet 3.0 spec.
I.e., the exception throwing approach suggested by C. Caldarale in
the next answer. Yes, it's neat. So I was overcomplicating it.
or
> From: Olivier Lefevre [mailto:lefev...@yahoo.com]
> Subject: Re: Getting the Tomcat shutdown port
> > Your application may be on a shared Tomcat instance someday
> > and System.exit is really bad in that case.
> So let's kill the servlet instead.
The servlet, or the
On 28/02/2011 16:59, Olivier Lefevre wrote:
>> Your application may be on a shared Tomcat instance someday
>> and System.exit is really bad in that case.
>
> True. So let's kill the servlet instead.
If you want to stop a single Servlet then Servlet.init() is the place to
it. See section 2.3.2 of
Your application may be on a shared Tomcat instance someday
and System.exit is really bad in that case.
True. So let's kill the servlet instead. But it's still unclear
how you'd do that because from the ServletConfig you can get the
ServletContext but from the ServletContext you can no longer ge
On 28/02/2011 16:12, Olivier Lefevre wrote:
>> Doing this from a servlet begs the question how you are going
>> to restart it.
>
> Not an issue: I want to shut it down at startup if some needed
> resources cannot be found. No pint restarting it then.
Fair enough. I wouldn't do it in a Servlet.ini
Doing this from a servlet begs the question how you are going
to restart it.
Not an issue: I want to shut it down at startup if some needed
resources cannot be found. No pint restarting it then.
I'm also curious why you want tot do this but System.exit() will
have exactly the same result as us
On 28/02/2011 15:34, Olivier Lefevre wrote:
> Is there a programmatic way to retrieve it from within
> a webapp, more exactly from within Servlet.init()? I
> can't find one. Same question for the actual command.
>
> As you may have guessed, I want to shut down Tomcat by
> opening a socket and send
Is there a programmatic way to retrieve it from within
a webapp, more exactly from within Servlet.init()? I
can't find one. Same question for the actual command.
As you may have guessed, I want to shut down Tomcat by
opening a socket and sending it a SHUTDOWN or whatever.
Maybe there is a less lo
Hi Konstantin,
I see... :-)
Thanks a lot,
János
On Feb 1, 2011, at 11:39 AM, Konstantin Kolinko wrote:
> 2011/2/1 János Löbb :
>> It is Tomcat 6.0.29 on OSX 10.6.5. If I ssh to the machine and shutdown
>> Tomcat and later boot it back again, all those components which are using
>> AWT are n
2011/2/1 János Löbb :
> It is Tomcat 6.0.29 on OSX 10.6.5. If I ssh to the machine and shutdown
> Tomcat and later boot it back again, all those components which are using AWT
> are not usable. However if I Apple Remote Desktop to the machine, open up
> Terminal there, shut down Tomcat and sta
Hi,
It is Tomcat 6.0.29 on OSX 10.6.5. If I ssh to the machine and shutdown Tomcat
and later boot it back again, all those components which are using AWT are not
usable. However if I Apple Remote Desktop to the machine, open up Terminal
there, shut down Tomcat and start it up, all AWT compone
Carl wrote:
...
Hi. Nothing to do with the subject, but I guess that either your
workstation or your email forwarding system must be off by one hour,
making your questions appear after the answer has already been given.
This looks strange, and reminds me of a character in one of Terry
Pratchett
Dear All,
> I don't believe Tomcat has any System.exit calls in it, so you could
> grep your code looking for such calls.
Note that findbugs can be used for that. It will issue a warning for code that
calls System.exit().
--
Kees Jan
http://java-monitor.com/
kjkos...@kjkoster.org
06-51838192
On 16/04/2010 23:43, Carl wrote:
> I thought thta a System.exit call would kill the JVM and would therefore
> not show the clean shutdown in the logs that the OP is seeing... am I
> wrong about System.exit?
Yes. It invokes the shutdown hook and that performs a clean shutdown.
Mark
nt: Friday, April 16, 2010 3:58 PM
Subject: Re: Tomcat Shutdown suddenly / random
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harry,
On 4/16/2010 2:35 PM, Harry Metske wrote:
could it be that something is sending your tomcat process a TERM signal,
logfiles in /var/log might tell someth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harry,
On 4/16/2010 2:35 PM, Harry Metske wrote:
> could it be that something is sending your tomcat process a TERM signal,
> logfiles in /var/log might tell something ?
> or one of your applications issues a System.exit() under certain
> circumstance
Peter,
could it be that something is sending your tomcat process a TERM signal,
logfiles in /var/log might tell something ?
or one of your applications issues a System.exit() under certain
circumstances ?
regards,
Harry
2010/4/16 Peter Borkowski
> Hi folks,
>
> we are facing a serious problem
On 16/04/2010 17:21, Peter Borkowski wrote:
> Hi folks,
>
> we are facing a serious problem with our tomcat which shuts itself down
> after some time of running. this problem first arises after we switched
> to our new server.
> we are using tomcat 6.0.26 (also tried different other 5.5.x, 6.0.x
>
Hi folks,
we are facing a serious problem with our tomcat which shuts itself down
after some time of running. this problem first arises after we switched
to our new server.
we are using tomcat 6.0.26 (also tried different other 5.5.x, 6.0.x
versions).
the "old" server was a 32 bit red hat ente
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: tomcat shutdown: catalina.sh STOP vs SIGTERM
>
> I'm not sure why it would take 20-30 seconds for you to see
> the above message: it should be immediate.
One possible cause is specifying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 3/8/2010 2:56 PM, Aggarwal, Ajay wrote:
> When I send SIGTERM to tomcat, I actually do get
>
> 1) these messages in my catalina.out
>
> Mar 8, 2010 2:46:05 PM org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
2010/3/8 Aggarwal, Ajay :
> When I send SIGTERM to tomcat, I actually do get
>
Tomcat installs a shutdown hook into JVM so that it will shutdown gracefully.
There is a problem though that if there are several shutdown hooks
then they run in parallel. That is particularly visible in 6.0.24,
becaus
---
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, March 08, 2010 1:33 PM
To: Tomcat Users List
Subject: Re: tomcat shutdown: catalina.sh STOP vs SIGTERM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 3/8/2010 12:53 PM, Aggarwal, Ajay wrote:
>
On Mon, Mar 8, 2010 at 9:53 AM, Aggarwal, Ajay
wrote:
> What is the downside of using SIGTERM, if any? It does seem to bring
> tomcat down in an orderly manner and much faster than "catalina.sh
> stop".
Yeah, "seem to" would be the operative phrase, I think.
A leap off a tall structure might "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 3/8/2010 12:53 PM, Aggarwal, Ajay wrote:
> Sometimes on a busy system I have seen that "catalina.sh stop" does take
> a long time to shutdown tomcat.
You might want to investigate why this is happening: my Tomcat instances
(we have 4 in prod
Sometimes on a busy system I have seen that "catalina.sh stop" does take
a long time to shutdown tomcat. We are running another "monitoring
service" on the system that monitors tomcat and few other system
services. After issuing "catalina.sh" and waiting for some time (up to
25 seconds) it loses pa
dBenjamin wrote:
Can you please suggest how to scan the port and check the port is used by
other application.
On what kind of system are you ?
Anyway, shut down Tomcat, then use the "netstat" command.
Depending on the system on which you are, there are options to this
command. Choose one that
Can you please suggest how to scan the port and check the port is used by
other application.
I am using socket programming to check the port this is right?
awarnier wrote:
>
> As I believe someone already told you, there is no need to repeat every
> message twice.
>
> dBenjamin wrote:
>> Tom
As I believe someone already told you, there is no need to repeat every
message twice.
dBenjamin wrote:
Tomcat not getting shutdown.. it shows the WARNING: StandardServer.await:
Invalid command '' received
can you pls find server.xml when I click shutdwon.bat server not listning
it shows WARNI
Tomcat not getting shutdown.. it shows the WARNING: StandardServer.await:
Invalid command '' received
can you pls find server.xml when I click shutdwon.bat server not listning
it shows WARNING: StandardServer.await: Invalid command '' received
can you please help me to solve this issues..
Tomcat1 wrote:
hi,
i have Tomcat 6.0.20. i config server.xml to work with SSL. the problem is
that Tomcat shutdown after randomaly period of time and doesnt restart
again.
Hi.
It is not very clear what your problem is. You have to be a bit more
specific in your explanation.
Also tell us on
work with SSL. the problem is
> that Tomcat shutdown after randomaly period of time and doesnt restart
> again.
> in server.xml i config:
>
>
>
>
>
> protocol="HTTP/1.1"
> maxThreads="150"
> scheme=
hi,
i have Tomcat 6.0.20. i config server.xml to work with SSL. the problem is
that Tomcat shutdown after randomaly period of time and doesnt restart
again.
in server.xml i config:
the log i get is:
Catalina.2009-12-21.log:
Dec 21, 2009 3:13
2009/12/19 SRama :
>
> before starting the server I am checking both port address if any other
> applicaion using the same port I am dynamicaly chaning the shutdown port and
> http port.
You won't be able to shutdown Tomcat using the shutdown script, if the
script does not know what Shutdown port
ache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
>> Dec 18, 2009 2:59:29 PM org.apache.catalina.core.StandardServer await
>> WARNING: StandardServer.await: Invalid command '' received
>> I am not able to
1 - 100 of 223 matches
Mail list logo
