David, you can have wget/Scheduled task on Win box
-Original Message-
From: David Wall [mailto:[EMAIL PROTECTED]
Sent: 05 Януари 2004 г. 20:54
To: Tomcat Users List
Subject: Re: Threaded servlets okay in a compliant container?
The use of a cron job that does a WGET on a URL that
The use of a cron job that does a WGET on a URL that triggers the background
processing sounds nice, but what's the process that triggers that on a
Windows box that doesn't have cron? A huge power of our application is that
it's written in Java and we can run it easily on Windows or Linux or
Solar
Ralph Einfeldt wrote:
The servlet has access to all information inside the container/context
that may be needed to do the job. For an external job this can be much
harder. (Iterate over all sessions to do something with them, access
attributes with application scope, access attributes from serve
ay, January 05, 2004 12:19 PM
> To: Tomcat Users List
> Subject: Re: Threaded servlets okay in a compliant container?
>
>
> Why is it easier to do those things from a Servlet, than a
> regular shell script?
>
-
Ralph Einfeldt wrote:
The cronjob is requesting an url with wget
and triggers tis way a servlet.
I understood the mechanism being used, I did not understand the benefit.
That's easy and sufficient to do regular jobs
like sending newsletters, cleaning up files,
that don't require any interaction)
ROTECTED]
> Sent: Monday, January 05, 2004 11:56 AM
> To: Tomcat Users List
> Subject: Re: Threaded servlets okay in a compliant container?
>
> Why would a cron triggered job benefit from Servlet container
> environment?
> Servlets are mainly for HTTP client/server interaction
Ralph Einfeldt wrote:
- Nobody (the spec included) prevents you from creating threads
You just have to follow some rules.
Yes, but it should make you think twice before indulging in something like that.
It also might prevent re-inventing the wheel.
- Besides creating threads I prefer to use se
;t have to deal with threads and the job
runs inside the servlet environment.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 31, 2003 1:46 AM
> To: Tomcat Users List
> Subject: Re: Threaded servlets okay in a compliant con
If we use our own connection pools and handle our own transactions
within the db, is there likely any issue with using other threads to do
background tasks that touch the database? I can see there may be issues
in a regular EJB world with declarative transactions and such (does EJB
have its ow
mewhere?)
> -Original Message-
> From: David Ramsey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 30, 2003 1:10 PM
> To: Tomcat Users List
> Subject: Re: Threaded servlets okay in a compliant container?
>
>
> SRV.9.11 says the same thing in the 2.4 spec so it
ments, you must be careful with how you manage them,
> > especially making sure they are appropriately terminated by your
> > application or by the JVM itself if they're daemons.
> >
> > Yoav Shapira
> > Millennium ChemInformatics
> >
> >
> >
> &g
propriately terminated by your
application or by the JVM itself if they're daemons.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: David Wall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 30, 2003 12:15 PM
To: [EMAIL PROTECTED]
Subject: Threaded servlets okay in a
lf if they're daemons.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: David Wall [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, December 30, 2003 12:15 PM
>To: [EMAIL PROTECTED]
>Subject: Threaded servlets okay in a compliant container?
>
>I recall r
I recall reading that conformant servlets and such (EJBs?) do not create
their own threads, something about being a container issue.
Does anybody know the primary objection to launching threads that take
on a life of their own? The container doesn't really need to manage it, per
se.
I suppose a c
14 matches
Mail list logo
