probleme with thread methodes (suspend & resume)

Question

3.50/5 (2 votes)

See more:

HI...
I have a problem with thread in suspend and resume methodes, j'ai toujours ce message here[^] ...thank you

this is the btnstart where i create the thread ...

C#

private void btnStart_Click(object sender, EventArgs e)
       {

           tbPort.ReadOnly = true;
           tbPath.ReadOnly = true;
           //la creation d'une list des socket
           int port = 0;
           port = Convert.ToInt16(tbPort.Text);
           string path = tbPath.Text;
           //alSockets = new ArrayList();
           Listener lst = new Listener(port, path, this.lbconnect);
           //creation d'une thread appeler thdlistener
           thdListener = new Thread(new ThreadStart(lst.listenerThread));
           //le debut de travail de thread...on utilisant la methode start
           thdListener.IsBackground = true;
           thdListener.Start();

           ////////////////////////////////
           btnStart.Enabled = false;
           Resume.Enabled = false;
           Suspend.Enabled = true;
           Stop.Enabled = true;
       }

and this is the button where i suspend the thread ...

C#

private void Suspend_Click(object sender, EventArgs e)
        {
           thdListener.Suspend();
           Resume.Enabled = true;
           Suspend.Enabled = false;
           lbConnections.Items.Add("Server Suspended");
        }

fanally the resume button ...

C#

private void Resume_Click(object sender, EventArgs e)
        {
            thdListener.Resume();
            Resume.Enabled = false;
            Suspend.Enabled = true;
            lbConnections.Items.Add("Server Resumed");
        }

i hope that you can find the problem...

Posted 24-Apr-11 3:47am

guendouz bachir

Updated 24-Apr-11 6:51am

Sergey Alexandrovich Kryukov

v3

Add a Solution

Comments

walterhevedeich 24-Apr-11 9:50am

You may want to post your code so others can further see the problem.

Kim Togo 24-Apr-11 10:34am

Please provide us with more info, code etc.

Oshtri Deka 24-Apr-11 11:27am

Warnings' messages have already answered to your question, you even have link to msdn. Suspend and Resume methods are obsolete.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kim Togo · Answer 1 · 2011-04-24T04:33:00

Solution 1

I do not know what type of class Listener is. But if it is a TcpListener[^] class, you can do:

C#

private void Suspend_Click(object sender, EventArgs e)
        {
           Listener.Stop(); // Closes the listener.
           Resume.Enabled = true;
           Suspend.Enabled = false;
           lbConnections.Items.Add("Server Suspended");
        }

C#

private void Resume_Click(object sender, EventArgs e)
        {
            Listener.Start(); // Starts listening for incoming connection requests.
            Resume.Enabled = false;
            Suspend.Enabled = true;
            lbConnections.Items.Add("Server Resumed");
        }

---

Thread.Suspend() and .Resume() is not the right way to halt and resume operation on a thread, you have no way to know how far you thread has come. (Hit "Obsolete")

Use other methods to reach your goal. Look at Thread Synchronization[^]

Posted 24-Apr-11 4:33am

Kim Togo

Updated 24-Apr-11 9:05am

v2

Comments

guendouz bachir 24-Apr-11 10:59am

see the code in down plz

Kim Togo 24-Apr-11 15:06pm

See my updated answer.

Sergey Alexandrovich Kryukov 24-Apr-11 13:02pm

Please see explanation and the alternative in my answer.
--SA

guendouz bachir 24-Apr-11 16:39pm

Mr Kim Togo you are wrong the tcplistener class don't contain start and stop methodes...

Kim Togo 25-Apr-11 2:09am

What documentation are you looking at? IF your "Listener(...)" is a class of TcpListener, then yes TcpListener.Start() and TcpListener.Stop() both exists.

Please see MSDN:

TcpListener.Start()
http://msdn.microsoft.com/en-us/library/system.net.sockets.tcplistener.start.aspx

TcpListener.Stop()
http://msdn.microsoft.com/en-us/library/system.net.sockets.tcplistener.stop.aspx

guendouz bachir 28-Apr-11 4:36am

i have understand what you have going to say but, i talk about thread and how to suspend and resume it?

Kim Togo 28-Apr-11 4:40am

You cannot suspend and resume threads. It is a bad design. I think you have to rethink the program design.

"Do not use the Suspend and Resume methods to synchronize the activities of threads. You have no way of knowing what code a thread is executing when you suspend it"

Sergey Alexandrovich Kryukov · Answer 2 · 2011-04-24T06:59:00

Do not use deprecated System.Threading.Thread.Suspend! Read the help page in this method to understand why:
http://msdn.microsoft.com/en-us/library/system.threading.thread.suspend.aspx[^].

Use an instance of System.Threading.EventWaitHandle. Your thread should use
EventWaitHandle.WaitOne, and UI thread will call on the same instance EventWaitHandle.Set (to wake up the waiting thread or allow thread to proceed if it was not in the waiting state at the call to WaitOne) or EventWaitHandle.Reset (to keep thread in a wait state).

Usually, you do not need to freeze the thread in any given point, which could not be accurate anyway (as if you used Suspend). At the same time, the thread will be awaken by Thread.Abort called in another thread.

—SA