Hi All,
I am using JSF framework for my project. I don't know if Tomcat is restcting
me or JSF framework is restricting me.
But I am unable to create and execute threads either in my JSF pages or my
managed beans.
I have created and exected threads successfully in this
Hi All,
I am using JSF framework for my project. I don't know if Tomcat is restcting
me or JSF framework is restricting me.
But I am unable to create and execute threads either in my JSF pages or my
managed beans.
I have created and exected threads successfully in this
Hello,
If I use threads, through the Thread class, how can I can finish them
whenever Tomcat reloads the application that created them.
Thanks.
Regards.
Daniel Molina Wegener
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
: threads in tomcat
Hello,
If I use threads, through the Thread class, how can I can finish them
whenever Tomcat reloads the application that created them.
Thanks.
Regards.
Daniel Molina Wegener
-
To unsubscribe, e-mail: [EMAIL
From: Daniel Molina (Inter-Media) [EMAIL PROTECTED]
If I use threads, through the Thread class, how can I can finish them
whenever Tomcat reloads the application that created them.
You can use a ServletContextListener which will be notified when the webapp
starts and stops. Implement the
Hello all,
I'm a newbie in mailing user list. My post is relationship with threads in
Tomcat Server 5.0. Over Debian Linux v3.0 rc 2, threads are shown like
processes; many processes are shown in process list command (ps -aux). We
think that most of them, except one or two are threads
Hi
Are there any solution about limit the process or threads count?. Remember
that Tomcat server.xml parameters don`t work.
For me, these settings work.
However, remember what they describe. They set the numbers of workers, not
total threads. You applicaton might spawn threads, tomcat might
shows Scheduler#shutdown which
should do what you want.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Jignesh Patel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 11, 2004 6:58 PM
To: Tomcat Users List
Subject: stopping all the java threads when
On Thu, Aug 12, 2004 at 11:57:04AM -0400, Jignesh Patel wrote:
: Thank you, we tried to stop using scheduler.shutdown method in quartz
: servlet's destroy method but it is not working as expected.
You *really* want to use a ContextListener for this: it provides the
equivalents of a servlet's
Hi All,
As on previous topic we discussed for developing listener to stop the
application. Now our confusion is we are using quartz application with
tomcat, so when we stop the tomcat it never stops. We want to develop a
listener which listens on stopping the server and in turn stops all the
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 11, 2004 6:58 PM
To: Tomcat Users List
Subject: stopping all the java threads when tomcat stops
Hi All,
As on previous topic we discussed for developing listener to stop the
application. Now our confusion is we are using quartz application with
tomcat
Hi,
I'm trying to understand how exactly Tomcat 5 is organized to work with
threads. Is there any documentation on how the connector is using the
threads? What happens in the thread pool, how exactly the are threads picked
from the pool and what is their state? And what happens with the released
available.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Angelov, Rossen [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 11:27 AM
To: 'Tomcat Users List'
Subject: Threads in Tomcat 5
Hi,
I'm trying to understand how exactly Tomcat 5 is organized to work
why do you want to use a thread to manage authentication? given the requestProcessor
threads are reused, it makes no sense to use the thread for the mapping.
you're better off just authenticating the first time and setting the HttpSession,
rather than look up the thread. I'm probably missing
2-3 years ago to work on iPlanet
and now I'm trying move them to Tomcat but it looks like there will be lot
of problems.
Ross
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 11:21 AM
To: Tomcat Users List
Subject: Re: Threads in Tomcat 5
but it looks like there will be lot
of problems.
Ross
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 11:21 AM
To: Tomcat Users List
Subject: Re: Threads in Tomcat 5
why do you want to use a thread to manage authentication? given
: Thursday, April 01, 2004 11:21 AM
To: Tomcat Users List
Subject: Re: Threads in Tomcat 5
why do you want to use a thread to manage authentication? given the
requestProcessor threads are reused, it makes no sense to use the thread for
the mapping.
you're better off just authenticating the first time
) based on the
product and the policy information. Each http session is related to an
eRights session.
Ross
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 12:26 PM
To: Tomcat Users List
Subject: RE: Threads in Tomcat 5
hit send too soon
information. Each http session is related to an
eRights session.
Ross
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 12:26 PM
To: Tomcat Users List
Subject: RE: Threads in Tomcat 5
hit send too soon. Another approach which I've used and is common
PROTECTED]
Sent: Thursday, April 01, 2004 6:27 PM
To: 'Tomcat Users List'
Subject: Threads in Tomcat 5
Hi,
I'm trying to understand how exactly Tomcat 5 is organized to
work with
threads. Is there any documentation on how the connector is using the
threads? What happens in the thread
Thanks to All, I have done all the stuff to make my web app thread safe,
It seems its fine for the moment.Except for a few more things.
It seems threading is realy complex. I am forking out a new thread in my
Handle request method and this is making the other request to wait for
the other thread
would use DB connection
pooling provided
by Tomcat.
I like 2. because I understand it is bad to open new threads in Tomcat.
I like 3 because I avoid having threads in Tomcat, but can get to DB thru
classes that are already in my Tomcat JVM via RMI. I do not like it because
it is more complex
would be in one place, and I would use DB
connection
pooling provided
by Tomcat.
It's also good because you will be able to easily monitor and manage the
DB threads via a web interface if you'd like.
I like 2. because I understand it is bad to open new threads in Tomcat.
You understand
Hello, Prince!
You wrote to Tomcat Users List [EMAIL PROTECTED] on Sat, 1 Nov 2003 13:21:42 +0530:
P Hi,
P I need to send a mail automatically at 10 minutes interval. how can
P i do this? how can i activate threads in tomcat?
Tomcat is a Java application, there are no difference of using
automatically at 10 minutes interval. how
can
P i do this? how can i activate threads in tomcat?
Tomcat is a Java application, there are no difference of using threads
with Tomcat or without it.
Simply expand Thread class, and run your thread.
But don't forget to notify and kill your thread when
Hi,
The problem is that stop / suspend are deprecated. The destroy() method
has yet not been implemented ? What does one do then?
I have a solution -
Keep a reference to the instances of the threads spawned in a
hashtable. In contextDestroy make all these references null . Will this
solution
Hi,
I need to send a mail automatically at 10 minutes interval. how can i do
this? how can i activate threads in tomcat?
regards
Prince
- Original Message -
From: Bill Barker [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November 01, 2003 1:00 PM
Subject: Re: Opinions
Use cron under unix and/or a java app that would use Javamail classes.
Of course you can do it inside a servlet.
- Original Message -
From: Prince [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Saturday, November 01, 2003 8:51 AM
Subject: HOW CAN I USE THREADS IN TOMCAT
PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Saturday, November 01, 2003 8:51 AM
Subject: HOW CAN I USE THREADS IN TOMCAT
Hi,
I need to send a mail automatically at 10 minutes interval. how can i do
this? how can i activate threads in tomcat?
regards
Prince
- Original Message
the Web app
shuts down.
Just a thought!
-Fred Whipple
iMagine Internet Services
-Original Message-
From: Erik Wright [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 01, 2003 11:03 AM
To: Tomcat Users List
Subject: Re: HOW CAN I USE THREADS IN TOMCAT
A servlet is just
Hi, I'm trying to get some info on the lifespan of a thread in tomcat
(4), can somebody point me to some documentation or help me out?
Cheers,
Josh
--
[ Josh 'G' McDonald ][ 0415 784 825 ][ http://www.gfunk007.com/ ]
-
To
The lifespan of a thread or request?
-Tim
Josh G wrote:
Hi, I'm trying to get some info on the lifespan of a thread in tomcat
(4), can somebody point me to some documentation or help me out?
Cheers,
Josh
-
To unsubscribe,
Tim Funk wrote:
The lifespan of a thread or request?
-Tim
A thread. Like when does tomcat decide to create them, and when they're
done servicing a request are they killed or simply put on hold back in
the pool to wait for the next request? And if they're kept alive, how
long before thet're
Ok. I don't know and wish not to know. (Prefer to see what the spec says with
respect to threads and obey that)
At a minimum, tomcat obeys the spec with respect to thread usage. Tomcat will
create the number of threads needed to serve the requests concurrently up to
the configured limit.
Millennium ChemInformatics
-Original Message-
From: Anton Tagunov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 1:37 AM
To: Tomcat Users List
Subject: Re[2]: [Q] Is it safe to create threads in Tomcat web-apps?
Hello Srevilak!
sgn However, if the three steps are IO-bound
jcrontab works ok, it is modeled after the unix crontab entries.
Best bet is to try it and see if it meets ones needs :)
Anton Tagunov wrote:
So, what John is speaking about - spending
less effort on thread coding and using an
existing solution (native Unix crontab)
may also be pushing you to
Hello Riaan!
RO (I have no idea what cron +wegt is???)
As John has explained
JT cron = scheduler
Unix world I would add to this :-)
And on the files (or directories involved
is named crontab, see bellow)
JT wget = command line HTTP/HTTPS client
both Unix and Windows
I just wanted to say that
Hello Srevilak!
sgn However, if the three steps are IO-bound, using multiple threads to
sgn run them concurrently can lead to a big improvement.
One might also consider using some kind of thread pooler in this
setting. Perhaps one could be crafted on top of
jakarta-commons-pool
-Anton
inconsistent
results because of the threads, so we had to remove
them.
Question is, how safe is it to create threads in a
Tomcat web-app? I would assume worker threads are
ok, i.e. threads you create to do a specific task and
then it terminates. When you are guaranteed the thread
will terminate either
threads in your application. Indeed,
when the application went live in a multi-server
clustered environment, we got very inconsistent
results because of the threads, so we had to remove
them.
Question is, how safe is it to create threads in a
Tomcat web-app? I would assume worker threads are
ok, i.e
of the threads, so we had to
remove
them.
Question is, how safe is it to create threads in a
Tomcat web-app? I would assume worker threads
are
ok, i.e. threads you create to do a specific task
and
then it terminates. When you are guaranteed the
thread
will terminate either because
went live in a multi-server
clustered environment, we got very inconsistent
results because of the threads, so we had to
remove
them.
Question is, how safe is it to create threads in a
Tomcat web-app? I would assume worker threads
are
ok, i.e. threads you create to do
.
Indeed,
when the application went live in a multi-server
clustered environment, we got very inconsistent
results because of the threads, so we had to
remove
them.
Question is, how safe is it to create threads in
a
Tomcat web-app? I would assume worker threads
Tomcat doesn't provide this but other simple solutions exist such as exposing
a URL and using cron + wget. (Some may also say kludge too)
As for aggregating statistics - I would recommend using a log file to record
the essential measurements then running your stats program on the logs. This
... nice suggestion, but I am delivering an
application as a .war file to a 3rd party and they
just want the .war (+ context.xml) with everything in
it hence, no other applications checking the logs
or database. All functionality must come from the .war
running in Tomcat. It is very important:
cron = scheduler
wget = command line HTTP/HTTPS client
The requirement for delivering everything in a WAR file is all nice and
dandy, but if you think about it, the requirement automatically breaks
the other requirement: scheduling.
If you cannot have a log file, and you cannot access a
Perhaps I should give a better explanation of how the
application works:
I deliver a .war file. I do have access to an
underlying database. The scheduled tasks perform more
on a is time reached than has time elapsed
principle... eg, it triggers when is it past
midnight? instead of has 24 hours
Nobody, from what I can tell, is saying can't. You did ask, though.
If you're willing to be diligent about coding your threads, go for it.
I think the point of previous posts was that in many cases, there is no
need for such a thing as your asking. There are always exceptions to
the rule,
You're right, no-one said I can't. :) I was hoping
someone who has actually used it could give some
feedback about it.
The (obvious) reason why the scheduled task also
cannot be active if the web-app is not active, is that
the scheduled task requires users to use web-app. Eg,
Friday at 15:00 you
Howdy,
I cannot see why creating a daemon thread cannot cater
for this. You just start the thread in the init method
of the InitServlet (or any servlet you create with
start-when-app-starts).
I'm actually a fan of the background daemon-thread approach, and think
the user-threading limitations
Yep, thanks... I've heard from other sources as well
that the ServletContextListener approach is better.
It gives me some comfort knowing other people find the
approach safe and without too many pitfalls. :)
--- Shapira, Yoav [EMAIL PROTECTED] wrote:
Howdy,
I cannot see why creating a
From: Tim Funk funkman () joedog ! org
Subject: Re: [Q] Is it safe to create threads in Tomcat web-apps?
You can create threads all day in tomcat, but here are the importnatn things
to consider:
- WHY! Are threads really the correct solution?
- And last but not least: WHY! Are threads
I am in total agreement and I have used user created threads on my site. I
view user created threads as a dangerous and usually un-needed thing.
Dangerous because of the side effects that aren't accounted for by more
junior programmers such as concurrency, shutting down the JVM (or lack of
threads in Tomcat web-apps?
You can create threads all day in tomcat, but here are the importnatn things
to consider:
- WHY! Are threads really the correct solution?
- And last but not least: WHY! Are threads really the correct solution?
I'm getting the impression that you think multiple
Hi,
When we ran a stress test on our application, it hang Tomcat service. We found an INFO
message in stderr a message below
INFO: All threads are busy, waiting. Please increase maxThreads or check the servlet
status200 200
I have tried to increase the maxProcessors in \conf\server.xml from
Will apache create on connection to tomcat for each child server, or for each thread?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
I have a number of threads that I would like to launch when tomcat
loads. until recently I was just using the first request to launch them
but I would prefer that they just started automatically when tomcat starts.
Is there any way to start new threads when tomcat is launched?
Thanks
Rob
to launch them
but I would prefer that they just started automatically when tomcat starts.
Is there any way to start new threads when tomcat is launched?
Thanks
Rob
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED
I hope that someone will be able to help.
I have tomcat 3.2 running on a Sun Solaris platform and on my Mac
OS-X. But after 5 to 10 hours Tomcat reaches some kind of deadlock on
the Sun. Now I know that this is NOT a Tomcat issue, it is my code.
But due to the length of time it takes to get
, enter
stop, then where all to get a stack dump.
-- Bill K.
-Original Message-
From: Ivan E. Markovic [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 23, 2001 4:28 AM
To: [EMAIL PROTECTED]
Subject: Tracking Threads inside Tomcat
Importance: High
Hi,
Anybody knows if it's posible encrease the number of threads with TOMCAT
3.2. I'm doing some performance testing and when I try to execute more that
100 request simultaneously I get the the error ...
2001-06-27 03:01:18 - ThreadPool: Pool exhausted with 100 threads.
It's posible
61 matches
Mail list logo
