Francois,
Do you have a shell application to be used as an example?
This looks really useful, but I have no idea on checking task lists and
termination other apps.
Regards,
Andy
Francois Piette wrote:
>> I think of adding several lines of code to monitor the listening status of
>> the TWSocket
> if the failure occurred at busy hours, even a two minutes service
> interruption will receive more than 10 complaints from customers.
> As I mentioned before, very demanding. :~(
If the customers are that demanding, you really need two or more servers
so you can tolerate downtime. My client
> Don't know if the reported state is accurate or not
I would not rely on the State property. Instead I would use the events. The
State property is anyway changed from the event handlers at the lower level.
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTE
Thanks to Francois, Wilfried and Angus for your kind response.
For monitoring the MySrv application at service level, I have already spawning
a process periodically to connect to MySrv and in case it fails, an alarm is
triggered. What I am trying to do is to find the root cause.
Francois,
> Yo
> Back to implementation, is there a way to do these steps:
> 1. Periodically check the state of TWSocket
> 2. If it is not listening, put it to listen again
> 3. If no response from TWSocket, destroy it and create a new
> instance
There is no reason for a socket to stop listening. I've got an I
Hello Patrick,
You can also write an event handler in OnSessionClose event. From ther
you can post a message to a custom message handler to let it listen
again.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Thursday, January 31, 2008, 13:24
> Back to implementation, is there a way to do these steps:
> 1. Periodically check the state of TWSocket
> 2. If it is not listening, put it to listen again
> 3. If no response from TWSocket, destroy it and create a new instance
You can have one TWSocket connect to another one within the same
app
>
> I have this "guard" mechanism implemented in several of my application. It
> is also implemented in many other application. Basically you write a
> second
> independent application which monitor the main application. Exactly what
> monitoring means depends on the application. In your case, you
> I think of adding several lines of code to monitor the listening status of
> the TWSocket, in case it was not the code kicks start it to listen again.
> This can help me to identify whether the problem is from the main thread.
> Can anybody kindly advise how to implement this mechanism?
I have t
Dear all,
I have an application derived mostly from the ICS's MtSrv example (I call it
MySrv hereafter). MySrv follows MtSrv in maintaining a listening socket in the
main thread, and creating a new client thread when a new socket is connected.
Client thread (socket) creation rate is around 5-
10 matches
Mail list logo
