[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Threading in .net

Posted on 2009-04-14
7
Medium Priority
?
243 Views
Last Modified: 2013-11-08
we are making an application which requires fetch from the database using a webservice. Until the fetch completes the application hangs. We incoroporated threads into the application both plain threads and background threads but none of them are able to bring the application out of the hang until the fetch completes. What could be wrong with our approach? we want a separate thread doing a fetch and doesnot effect the rest of the application!
0
Comment
Question by:sultansaadat
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
7 Comments
 
LVL 75

Expert Comment

by:käµfm³d 👽
ID: 24141053
Could you possibly post some code dealing with where you are creating the thread and where you are making the threaded call to the webservice?
0
 

Author Comment

by:sultansaadat
ID: 24141179
here goes the code. This one has a simple call to an online database.
 ClassDAL cdl = new ClassDAL();
 DataSet ds = new DataSet();
 void testThread()
        {
            
            
             if (InvokeRequired)
            {
                   
                MethodInvoker method = new MethodInvoker(testThread);
                Invoke(method);
                return;
            }
 
           
            ClassDAL cdl = new ClassDAL();
            //DataSet ds = new DataSet();
            ds = cdl.getAllProducts();
 
        
           
        }
 
 private void button1_Click(object sender, EventArgs e)
        {
         
            this.backgroundWorker1.RunWorkerAsync();
            
            
            
        }
 private void backgroundWorker1_DoWork(object sender, DoWorkEventArgs e)
        {
 
            testThread();
            //System.Threading.Thread.Sleep(500);
           
        }
 
        private void backgroundWorker1_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e)
        {
            dataGridView1.DataSource = ds;
            dataGridView1.DataMember = ds.Tables[0].TableName;
        }

Open in new window

0
 

Author Comment

by:sultansaadat
ID: 24141197
our thread is not running asynchronously!
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
LVL 6

Expert Comment

by:obrienslalom
ID: 24141968
Take a look at the documentation for the ISychronizeInvoke interface:
http://msdn.microsoft.com/en-us/library/system.componentmodel.isynchronizeinvoke_methods.aspx.
What happens with Invoke is that is basically just a call to BeginInvoke followed by a call to EndInvoke.  Invoke will be a synchronous call.
0
 

Author Comment

by:sultansaadat
ID: 24141991
Thanks. I will try the code now! :)
0
 

Author Comment

by:sultansaadat
ID: 24142027
basically we wont have to create other threads?
0
 
LVL 6

Accepted Solution

by:
obrienslalom earned 2000 total points
ID: 24144223
I am not going to say that you don't need another thread.  That is what the BackGroundWorker will do for you.  What you are running into in your case is a bit odd actually.  A little background might be needed.

Imagine you have a single GUI thread, which creates a bunch of controls. Now you spawn off another thread to perform some work. This new thread shouldn't be able to update the controls created and owned by the GUI thread.

Invoke/BeginInvoke transfers the tasks onto the GUI threads. That is why you are seeing an unresponsive interface.  You are spawning a background worker, which just transfers the work right back to the original thread.

So, basically, you don't need to use Invoke unless you are updating the controls on the GUI.  So do as much work as you can first, then use Invoke when you have to (which will be any cross-thread updates).
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
Calculating holidays and working days is a function that is often needed yet it is not one found within the Framework. This article presents one approach to building a working-day calculator for use in .NET.
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
In a question here at Experts Exchange (https://www.experts-exchange.com/questions/29062564/Adobe-acrobat-reader-DC.html), a member asked how to create a signature in Adobe Acrobat Reader DC (the free Reader product, not the paid, full Acrobat produ…

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question