500pts: Not all events are arriving in my thread, please help

Please show your code.

Hi alexfm,

Thanks... Ok yes of course... its quite simple.. the thing to remember is that it does work as far as the events do arrive with statusCode LOADING but never loaded unless i put the thread.sleep .... i think its something to do with threads... but a little unsure.

This is from the main GUI form ... i start the thread passing in

// This is just a class which i use to pass in a variable to a thread..
ThreadMarket threadMarket = new ThreadMarket(market);

_workerThread = new Thread(new ThreadStart(threadMarket.ProcessMarket));
                        _workerThread.Name = market;
                        _threads.Add( market, _workerThread );
                        _workerThread.IsBackground = true;
                        _workerThread.Start();

Then in the thread itself U(the class)... i have the following ....... _stcs is a hashtable which holds a number of stock items.

            private void SubscribeToMarkets(string market)
            {
                  // Iterate through all of the stocks
                  for (int j = 0; j < _stcs.Count; j++)
                  {
                        if ( (_stcs[j] as Stock).Market == market) // Do we have an stock in the current market?
                        {
                              // Yes - then lets process it
                              string stockInstance = (_stcs[j] as Stock).STC;
                              string marketInstance = (_stcs[j] as Stock).Market;
                              User localmyUser = MonitorForm.MainForm.GetUser;
                              
                              Console.WriteLine("sub to : " + marketInstance + "/" + stockInstance );
                              
                        
                              CliCommon.Stock stock= new Stock (localmyUser,stockInstance , marketInstance );
                              _myStocks.Add(stockInstance ,stock);
                              stock.view.xml = MonitorForm.MainForm.GetXml;
                              stock.view.np = 1;


                              // Subscribe to the event for receiving
                              stock.statusChanged +=new StatusChanged(stock_statusChanged);
                              Thread.Sleep(5000);
                              stock.load();
                        }
                  }
            }


and the event


            private void stock_statusChanged(object sender)
            {
                  //System.Windows.Forms.Application.DoEvents();
                  Stock stock= sender as Stock;
                  if(stock.status == Stock.statusCode.LOADED)
                  {
                        stock.statusChanged -=new StatusChanged(stock_statusChanged);
                        

                              ///////////// NEVER ARRIVES HERE UNLESS I PUT A THREAD.SLEEP but even then some things are missing..

                  }
                  else
                  {
                        //Thread.Sleep(5000);
                  }
            }

stock.statusChanged -=new StatusChanged(stock_statusChanged);

This line unsubscribes from statusChanged event. After this line stock_statusChanged function is not called. Is this your intention?

Yes ... because ... once its status is loaded.. i unsubscribe so that i don't receive more evetns for that stock..

It is in the IF statement when its loaded but without the Thread.sleep ... it never arrives...

Ian

What happens in the Stock class? Does it raise this event, what is thread context where this event is raised? Event is always raised in the context of thread where raising code is executed.

What is the purpose of this line:
Thread.Sleep(5000);        // SubscribeToMarkets

Hi AlexFM... The stock component belongs to somebody else... i am only using it... but I have just been in contact with him... and he has informed me that we might be running out of threads in thread pool....

Be in contact shortly

Ian

Thanks AlexFM,

its sorted now.... it appears that the class (not mine) was using too many threads... it is now resolved...

thanks

ian