> 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.
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
> ------------------------------------------------------------------------
>