- is not part of the servlet spec. It will not appear in tomcat.
-Tim
Mark wrote:
run-at is 2.4 spec and I think Tomcat 4 _IS_NOT_ Servlet 2.4 spec
My guess it will work in Tomcat 5.0.X and above.
Comments?
-
To unsubscribe, e-m
run-at is 2.4 spec and I think Tomcat 4 _IS_NOT_ Servlet 2.4 spec
My guess it will work in Tomcat 5.0.X and above.
Comments?
Mark.
--- Dwayne Ghant <[EMAIL PROTECTED]> wrote:
> Have fun I hope this helps!!! It should.
>
>
>
> servlet-class='test.HelloWorld'>
>
>
>
>
>
> The
> Will be the the RUN-AT-paramter evaluated by Tomcat 5.0x or by anybody else?
Use an external scheduler like Quartz or Flux.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
-
To un
is resin specific (non servlet compliant extension)
-Tim
Thomas Chille wrote:
On Tue, 21 Dec 2004 20:24:25 -0800, Dwayne Ghant <[EMAIL PROTECTED]> wrote:
The alarm is configured as any other servlet, with the addition of the
run-at tag. The following configuration runs the servlet every 15
minutes
On Tue, 21 Dec 2004 20:24:25 -0800, Dwayne Ghant <[EMAIL PROTECTED]> wrote:
> The alarm is configured as any other servlet, with the addition of the
> run-at tag. The following configuration runs the servlet every 15
> minutes. If the hour is missing, e.g. :15 the service is run at the
> specified
Frank W. Zammetti wrote:
I think what you describe is probably more properly implemented as
some sort of queueing system. Something along the lines of setting up
a queue on each data collection server that "lazily" updates the
central server (there's other ways to structure it of course).
Othe
I think what you describe is probably more properly implemented as some
sort of queueing system. Something along the lines of setting up a
queue on each data collection server that "lazily" updates the central
server (there's other ways to structure it of course).
Otherwise, I myself would ten
Frank W. Zammetti wrote:
Dennis Payne wrote:
Frank,
I'm using threads and didn't know I was vulnerable.
I'm not sure "vulnerable" is really the right word, but I'll go with
it :)
Here's how I've done it. I created a class that implements runnable
and call its initialize method from a servlet
The minimum thread priority is 1, maximum is 10 and medium or normal is 5. See:
http://java.sun.com/j2se/1.4.2/docs/api/constant-values.html#java.lang.Thread.NORM_PRIORITY
You can set a "good neighbor poilicy with MIN_PRIORITY. Hunter on
Servlets covers this with a daemon servlet.
Jack
On Tu
Dennis Payne wrote:
Frank,
I'm using threads and didn't know I was vulnerable.
I'm not sure "vulnerable" is really the right word, but I'll go with it :)
Here's how I've
done it. I created a class that implements runnable and call its
initialize method from a servlet init method at application
Dennis Payne wrote:
If you are running Linux or Unix check the syntax for the 'nice'
command.
[EMAIL PROTECTED] 12-27-2004 18:55 >>>
Frank W. Zammetti wrote:
It's interesting, Craig and I had an exchange about threads in
servlet
containers last week... I can't find a link to
If you are running Linux or Unix check the syntax for the 'nice'
command.
>>> [EMAIL PROTECTED] 12-27-2004 18:55 >>>
Frank W. Zammetti wrote:
> It's interesting, Craig and I had an exchange about threads in
servlet
> containers last week... I can't find a link to the thread
unfortunately.
>
> An
Frank W. Zammetti wrote:
It's interesting, Craig and I had an exchange about threads in servlet
containers last week... I can't find a link to the thread unfortunately.
Anyway, the basic idea behind that "don't spawn your own threads
inside a servlet container" admonishment is based more on the
Jukka Uusisalo wrote:
Jorge Sopena wrote:
Why is bad using own threads inside web application?
Aren't all the servlet request actually a thread in Tomcat?
I can't find a reason why it's so bad solution.
I think that comes from J2EE specs. I do not remember is threads just
forbidden but if you foll
Use java.util.Timer and java.util.TimerTask. Create a Timer object.
Timer timer = new Timer(). Then create a TimerTask object. SomeTask
task = new SomeTasK().
private class SomeTask
extends TimerTask {
public void run() {
// do stuff
}
}
Schedule the task: timer.sche
"[OT]Threads and Servlets Question" on the struts-user list.
Jack
On Tue, 21 Dec 2004 18:17:40 -0500, Frank W. Zammetti
<[EMAIL PROTECTED]> wrote:
> It's interesting, Craig and I had an exchange about threads in servlet
> containers last week... I can't find a link to the thread unfortunately.
>
Why don't you guys use something like Lea's multithreading queues?
Jack
On Tue, 21 Dec 2004 18:14:30 +0100, Jorge Sopena <[EMAIL PROTECTED]> wrote:
> Hi,
> I'm having a similar problem in my application.
> I've got several servlets called by the users. Every requets save some
> information in DB
gt; -Original Message-
> > > From: Shilpa Nalgonda [mailto:[EMAIL PROTECTED]
> > > Sent: 21 December 2004 16:14
> > > To: Tomcat Users List
> > > Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
> > >
> > >
> > > Tha
Shilpa Nalgonda [mailto:[EMAIL PROTECTED]
> > Sent: 21 December 2004 16:14
> > To: Tomcat Users List
> > Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
> >
> >
> > Thanks for the reply...
> >
> > The application which i am trying to
ECTED]
Onderwerp: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
It is possible to create a servlet thread in the init() method. That
thread sould stay alive and run something every thirty minutes. The
issue of pushing information out to the user remins the same. The
servlet an
->
REQUEST INFO >
<--- RESPONSE
<-- RESPONSE
-Original Message-
From: Wade Chandler [mailto:[EMAIL PROTECTED]
Sent: 21 December 2004 16:03
To: Tomcat Users List
Subject
-REQUEST INFO >
<--- RESPONSE
<-- RESPONSE
-Original Message-
From: Wade Chandler [mailto:[EMAIL PROTECTED]
Sent: 21 December 2004 16:03
To: Tomcat Users List
Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
Shilpa N
Have fun I hope this helps!!! It should.
The value is a list of 24-hour times when the servlet should be
automatically executed. To run the servlet every 6 hours, you could use:
0:00, 6:00, 12:00, 18:00
Frank W. Zammetti wrote:
Your just lending weight to what I said... Don't play with
Your just lending weight to what I said... Don't play with threads in a
servlet contain unless your really sure you have to and are really sure
you can do it safely :)
(I'm not sure I knew init() could be called more than once, certainly I
didn't remember when I wrote that, so excellent point)
On Tue, Dec 21, 2004 at 03:37:26PM -0700, Dennis Payne wrote:
: It is possible to create a servlet thread in the init() method. That
: thread sould stay alive and run something every thirty minutes.
Yes and no. ;)
It's possible to use a servlet's init() method for this; but per the
spec, containe
It's interesting, Craig and I had an exchange about threads in servlet
containers last week... I can't find a link to the thread unfortunately.
Anyway, the basic idea behind that "don't spawn your own threads inside
a servlet container" admonishment is based more on the fact that it's
quite eas
At 05:37 PM 12/21/2004, you wrote:
It is possible to create a servlet thread in the init() method. That
thread sould stay alive and run something every thirty minutes. The
issue of pushing information out to the user remins the same. The
servlet and the thread cannot do that. On the other hand,
to run servlet for every 30 minutes in Tomcat 4.1.30
It is possible to create a servlet thread in the init() method. That
thread sould stay alive and run something every thirty minutes. The
issue of pushing information out to the user remins the same. The
servlet and the thread cannot do that
It is possible to create a servlet thread in the init() method. That
thread sould stay alive and run something every thirty minutes. The
issue of pushing information out to the user remins the same. The
servlet and the thread cannot do that. On the other hand, it is
possible to setup java scrip
Jorge Sopena wrote:
Why is bad using own threads inside web application?
Aren't all the servlet request actually a thread in Tomcat?
I can't find a reason why it's so bad solution.
I think that comes from J2EE specs. I do not remember is threads just
forbidden but if you follow specs, you do not kn
, 2004 12:21 PM
To: Tomcat Users List
Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
myself and ben have suggested the most appropriate methods for doing this.
Ben mentions WGET http://www.gnu.org/software/wget/wget.html which can be
added to a *basic* script hooked up to a
, 2004 11:41 AM
To: Tomcat Users List; Billy Talton
Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
My application has to use the connection pooling of Tomcat to talk to the
database...
and all my Database access classes are deployed om Tomcat...so if i just
write a java
, 2004 11:03 AM
To: Tomcat Users List
Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
Shilpa Nalgonda wrote:
> Hi,
> I am using Tomcat4.1.30 version.
> I have to develop a client application which looks in the database every
30
> minutes,
> to retrieve the status
Tomcat Users List <[EMAIL PROTECTED]>
>Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
>Date: Tue, 21 Dec 2004 18:58:23 +0100
>
>Why is bad using own threads inside web application?
>Aren't all the servlet request actually a thread in Tomcat?
>I can&#
L PROTECTED]>
Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
Date: Tue, 21 Dec 2004 18:58:23 +0100
Why is bad using own threads inside web application?
Aren't all the servlet request actually a thread in Tomcat?
I can't find a reason why it's so bad solution.
I
t rid of threads and thread sleeps inside web application
code.
Allistair.
-Original Message-
From: Jorge Sopena [mailto:[EMAIL PROTECTED]
Sent: 21 December 2004 17:15
To: Tomcat Users List
Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
Hi,
I'm having a similar
External scripts really are the best answer for this. It is not
possible to 'PUSH' information like this without a dedicated client!
>>> [EMAIL PROTECTED] 12-21-2004 10:14 >>>
Hi,
I'm having a similar problem in my application.
I've got several servlets called by the users. Every requets save som
Use cron in Unix/Linux or task scheduler in Windows.
>>> [EMAIL PROTECTED] 12-21-2004 08:44 >>>
Hi,
I am using Tomcat4.1.30 version.
I have to develop a client application which looks in the database
every 30
minutes,
to retrieve the status of an order and send the status to the remote
client.
Aga
inside web application
code.
Allistair.
> -Original Message-
> From: Jorge Sopena [mailto:[EMAIL PROTECTED]
> Sent: 21 December 2004 17:15
> To: Tomcat Users List
> Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
>
>
> Hi,
> I'
Hi,
I'm having a similar problem in my application.
I've got several servlets called by the users. Every requets save some
information in DB, that has to be sent to another server later and in a
compress format.
So I need sth similar toShilpa is asking, a process which runs every X
minutes to r
-
> From: Shilpa Nalgonda [mailto:[EMAIL PROTECTED]
> Sent: 21 December 2004 16:41
> To: Tomcat Users List; Billy Talton
> Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
>
>
> My application has to use the connection pooling of Tomcat to
> talk to th
Talton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 21, 2004 11:41 AM
To: Tomcat Users List
Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
Why are you writing a servlet for this? If the application does not
use any of the services confined to the Servlet API and Tomcat
Laba diena.
Dėkojame, kad mums parašėte.
Jūsų atsiųsta žinutė išsaugota mūsų duomenų bazėje.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
Date: Tue, 21 Dec 2004 16:28:49 -
no, and I believe doing so it bad practice. use some OS controlled timer
like cron to issue a HTTP call to
On Tue, 2004-12-21 at 11:28, Allistair Crossley wrote:
> no, and I believe doing so it bad practice. use some OS controlled timer like
> cron to issue a HTTP call to your servlet. I once wrote a shell script that
> calls a http address on the local machine but cannot remember how ;) if you
> are
ite this servlet utility.
> > This is the reason why chose to use servlet, but is there any
> > configurable
> > parameter to run servlet for every 30 minutes...
> >
> > -Original Message-
> > From: Wade Chandler [mailto:[EMAIL PROTECTED]
> > Sent: Tu
database itself.
don't add a thread into your web application.
> -Original Message-
> From: Shilpa Nalgonda [mailto:[EMAIL PROTECTED]
> Sent: 21 December 2004 16:14
> To: Tomcat Users List
> Subject: RE: How to run servlet for every 30 minutes in Tomcat 4.1.30
>
&g
List
Subject: Re: How to run servlet for every 30 minutes in Tomcat 4.1.30
Shilpa Nalgonda wrote:
> Hi,
> I am using Tomcat4.1.30 version.
> I have to develop a client application which looks in the database every
30
> minutes,
> to retrieve the status of an order and send the statu
Hello, Shilpa,
With Wade, I wonder what you want. Apparently you have a client
making and order and being informed about the status of the order.
You say you have to develop a "client application" which looks to the
database. Since this is a Tomcat list, that would seem to be a
"server applicat
-REQUEST INFO >
<--- RESPONSE
<-- RESPONSE
> -Original Message-
> From: Wade Chandler [mailto:[EMAIL PROTECTED]
> Sent: 21 December 2004 16:03
> To: Tomcat Users List
> Subject: Re: How to run servlet for every 30 mi
:44
An: Tomcat Users List
Betreff: How to run servlet for every 30 minutes in Tomcat 4.1.30
Hi,
I am using Tomcat4.1.30 version.
I have to develop a client application which looks in the database every 30
minutes,
to retrieve the status of an order and send the status to the remote client.
Again
Shilpa Nalgonda wrote:
Hi,
I am using Tomcat4.1.30 version.
I have to develop a client application which looks in the database every 30
minutes,
to retrieve the status of an order and send the status to the remote client.
Again waits for the
The client's response and insert the repsonse back to the
Hi,
I am using Tomcat4.1.30 version.
I have to develop a client application which looks in the database every 30
minutes,
to retrieve the status of an order and send the status to the remote client.
Again waits for the
The client's response and insert the repsonse back to the database.
I wanted to
53 matches
Mail list logo
