On 28.07.2010 01:01, Robinson, Eric wrote:
2) Use System.getRuntime().addShutdownHook() to trigger your
own thread when the JVM does decide to exit.
Assuming the OP does not have easy access to the running
application, would that mean adding another application
which is launched at Tomcat
So we definitely know the process is gone and not that
it is only no longer responding?
I'm not 100% certain. I did...
netstat -an|grep :3057|grep LISTEN
..and nothing came back. From that we at least know that the process
was no longer listening on its assigned port.
Then I
try to change shutdown port in the server.xml
--
View this message in context:
http://old.nabble.com/Tomcat-Shutting-Down-by-Itself--tp29249881p29293203.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
Robinson, Eric wrote:
What kind of machine are you running these 163/164
instances of Tomcat on, and when you are running them,
what /does/ free say ?
I have two different servers with 164 instances of tomcat. Both servers
have 2x quad-core 2.8Ghz Xeon processors with 32GB RAM. On the first
Intuitively, I would have never thought that it was
/possible/ to run 160 or so instances of Tomcat on
anything but some type of very expensive hardware.
I assure you that it works admirably! And each of the instances runs a
sophisticated medical application with hundreds of JSPs and class
Robinson, Eric wrote:
Intuitively, I would have never thought that it was
/possible/ to run 160 or so instances of Tomcat on
anything but some type of very expensive hardware.
I assure you that it works admirably! And each of the instances runs a
sophisticated medical application with
364600 491072 java5101 --Here's the occasional bad boy
604780 746120 java 31131 --Here's the occasional bad boy.
Those sizes appear to be in Kbyte, so we are talking in one
case of a process with a resident size of 360 MB, in the other of
600 MB.I guess thus, that
Yes. Each instance serves a different set of users
in a local office somewhere.
By that I mean each pair of load-balanced instances serves a set of
users in a local office somewhere.
--
Disclaimer - July 27, 2010
This email and any files transmitted with it are confidential and intended
Robinson, Eric wrote:
Yes. Each instance serves a different set of users
in a local office somewhere.
By that I mean each pair of load-balanced instances serves a set of
users in a local office somewhere.
Then my suspicions would be as follows :
this particular set of users of this complex
André Warnier wrote:
Robinson, Eric wrote:
Yes. Each instance serves a different set of users in a local office
somewhere.
By that I mean each pair of load-balanced instances serves a set of
users in a local office somewhere.
Then my suspicions would be as follows :
this particular set of
this particular set of users of this complex application, uses
a particular functionality of the application, used by no other
set of users, and that particular functionality contains
(or triggers) a bug that blows away the server.
That seems like the reasonable conclusion. The next
On 27/07/2010 21:20, Robinson, Eric wrote:
this particular set of users of this complex application, uses
a particular functionality of the application, used by no other
set of users, and that particular functionality contains
(or triggers) a bug that blows away the server.
That seems
Mark Thomas wrote:
On 27/07/2010 21:20, Robinson, Eric wrote:
this particular set of users of this complex application, uses
a particular functionality of the application, used by no other
set of users, and that particular functionality contains
(or triggers) a bug that blows away the server.
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: Tomcat Shutting Down by Itself?
Would there be any specific way to catch a call to system.exit() ?
1) Enable a SecurityManager (usually a major pain).
2) Use System.getRuntime().addShutdownHook() to trigger your own thread when
Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: Tomcat Shutting Down by Itself?
Would there be any specific way to catch a call to system.exit() ?
1) Enable a SecurityManager (usually a major pain).
Because you would need to authorise everything else
2) Use System.getRuntime().addShutdownHook() to trigger your
own thread when the JVM does decide to exit.
Assuming the OP does not have easy access to the running
application, would that mean adding another application
which is launched at Tomcat start, and runs the above ?
Or do you
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: Tomcat Shutting Down by Itself?
1) Enable a SecurityManager (usually a major pain).
Because you would need to authorise everything else that this
application /might/ be doing, except system.exit(), right ?
Correct. Getting
What I was trying to say above, in a devious but humoristic
way, is that there are not a lot of people on this list
running those versions anymore.
Fair enough. I realize it's old, but it still works great for 163 of the
164 instances on this server. However, an upgrade is coming soon and
Robinson, Eric wrote:
What I was trying to say above, in a devious but humoristic
way, is that there are not a lot of people on this list
running those versions anymore.
Fair enough. I realize it's old, but it still works great for 163 of the
164 instances on this server. However, an
What kind of machine are you running these 163/164
instances of Tomcat on, and when you are running them,
what /does/ free say ?
I have two different servers with 164 instances of tomcat. Both servers
have 2x quad-core 2.8Ghz Xeon processors with 32GB RAM. On the first
server (app03), most
From: Robinson, Eric [mailto:eric.robin...@psmnv.com]
Subject: Tomcat Shutting Down by Itself?
We've observed tomcat5
Tomcat 5.x.y what? Be specific. Also tell us the JVM you're using and the
platform you're running on.
shutting down seemingly by itself recently. This
morning I saw
On 23.07.2010 19:43, Robinson, Eric wrote:
We've observed tomcat5 shutting down seemingly by itself recently. This
morning I saw this in the log:
- Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
Any way to tell why tomcat is shutting down?
Maybe something from this recent
Tomcat 5.x.y what? Be specific. Also tell us the JVM
you're using and the platform you're running on.
Apache Tomcat/5.0.28
Java 1.4.2_09-b05 Sun Microsystems Inc.
Linux 2.6.18-92.1.22.el5PAE i386
If one of your webapps is doing something antisocial such
as calling System.exit(), that
Maybe something from this recent discussion applies:
http://marc.info/?t=12767355721r=1w=2
Good thread, thanks. Unfortunately, the situations it describes don't
apply in this case.
--
Eric Robinson
Disclaimer - July 23, 2010
This email and any files transmitted with it are confidential
Robinson, Eric wrote:
Tomcat 5.x.y what? Be specific. Also tell us the JVM
you're using and the platform you're running on.
Apache Tomcat/5.0.28
Java 1.4.2_09-b05 Sun Microsystems Inc.
Linux 2.6.18-92.1.22.el5PAE i386
Gentlemen,
I think we need a minute of silence here, and a golden
This Tomcat and Java are just trying to say, in the only
way they can, that after some 10 years of good and hard
labor, it is now time to retire them and have the burden
taken over by a new generation.
Yes, that's probably it. One of the...
[r...@app03 ~]# ps ax|grep java|wc -l
164
Robinson, Eric wrote:
This Tomcat and Java are just trying to say, in the only
way they can, that after some 10 years of good and hard
labor, it is now time to retire them and have the burden
taken over by a new generation.
Yes, that's probably it. One of the...
[r...@app03 ~]# ps ax|grep
27 matches
Mail list logo
