This isn't going to work. What you may want to consider is creating an NT
service to do this - as this is more closely suited to the kinds of things
you would choose service instead of web-service to do.
Web services are stateless - so a call to one method won't carry over to
the next method call. If enough time passes, the thread will time out. In
fact, if you are just creating a normal time on a web service thread, and
then returning, when that thread is reharvested, it's timer will get
orphaned (and eventually croak).
--------------------
>From: "Christina Haller" <codegen@gmx.net>
>Subject: Self running timer on Webservice??
[quoted text clipped - 10 lines]
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:5490
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 43 lines]
>
>End Sub
Christina Haller - 17 Feb 2005 14:45 GMT
Ok, that was what i assumed.
Because the webserver is not mine, I cant install any software on it.
But if found another solution for doing my (automated) backup.
Thanks anyway.
> This isn't going to work. What you may want to consider is creating an NT
> service to do this - as this is more closely suited to the kinds of things
[quoted text clipped - 72 lines]
>>
>>End Sub
taliesin77 - 23 Feb 2005 07:41 GMT
> *Ok, that was what i assumed.
> Because the webserver is not mine, I cant install any software on
[quoted text clipped - 4 lines]
>
> *
What was the other solution you found? I tried creating a pair of
webservices that accept a target URI to "signal" every given period for
a given total duration. These two services pass the state info back and
forth in their arguments and then send a "signal" (request) to wake up
the main web service. While the ping-ponging works, my threads still
randomly die (sometimes a few minutes, sometimes after 40 minutes of
ping-pong
Hopefully you found something else that works cause I am getting pretty
frustrated with having my threads just die.
Christina Haller - 08 Mar 2005 15:14 GMT
> What was the other solution you found? I tried creating a pair of
> webservices that accept a target URI to "signal" every given period for
[quoted text clipped - 6 lines]
> Hopefully you found something else that works cause I am getting pretty
> frustrated with having my threads just die.
I could not find a solution for the webservice.After I brought down my
Webspace Provider once :-s, I changed the approach. Instead of having a
continuosly running service on the webserver, I create my backup of the
database when the first user (per day) is login in to the application and
send via email to my workplace;-). That means, if someone changes data,
automatically the database has been saved once per day.
That replaces my need of the webservice.
Until now, I couldnt figure out the webservice stuff. It's really
complicated, but I think it has to do with the asynchronous call of the
webservice. If I find a solution, I'l post it here of course.
cheers
c.
> --
> taliesin77
> ------------------------------------------------------------------------
> Posted via http://www.codecomments.com
> ------------------------------------------------------------------------