Run Away Client

[Lawrence Staffieri]

I am running an older version, and I am wondering how this is addressed in the CSC… or if it is at all.

I have a client who is sending messages fast enough that they are dominating the data stream and no one else can connect to the thread.

Is there a way, on the server side, so cut the connection? or disallow communication from that client without having to restart the Client?

Thanks 🙂

Topic

[Corry Macfarlane]

Yes, the CSC Server side has controll of the client.  The server can restart the service, stop the service, or reconfigure it, etc.

Corry

[Lawrence Staffieri]

That is true.  However, it can only control the client if the client decides to ask the server for the commands… and in my experience that doesn’t happen until the inbound stream is completed.

This instance occurs when there is a flood of messages coming in.  I want to be able to tell the server to stop accepting messages from the CSC without the need to communicate to the CSC Client itself.

In our environment, if this condition happens… and no one is available on the Customer Side to address the CSC, there is no way to stop the flood.  Restart Commands don’t work, because they do not go across until the CSC asks for them.  The flood doesn’t stop because the CSC Client is overwelmed with input.  This condition Downs our interface to every other customer we have.

A switch on the server that says “No more messages from you” seems to be a need in this case.

Another option would be to limit the “Face Time” of Each CSC.  However, I am also unsure if that as been addressed.

Thanks 🙂

Larry Staffieri

Standing Stone Inc.

[Corry Macfarlane]

Here’s a screen shot of the controll commands in CSC 4.0.  I don’t have the latest CSC either at this point.

I wonder if “Suspend” will do anything.

Corry

[Lawrence Staffieri]

Same problem remains. The CSC needs to retrieve the command to execute it. 🙂

[Author]

Replies