Hi, I am confused the thread behaviour i am getting. Scenario is like this .. I am starting 2 threads one will read from the databse (using stored procedure).Both thread start and then once control comes to second thread which, is doing SP processing, it blocks the CPU (i.e control doesn't go back to thread 1). Is it because of socket issue? Regards,
What is your operating system? Some do time-slicing, some do round robin, some just run a thread until interrupted. What if you changed the priority of the thread that isn't getting a chance to run to a higher priority? Does that at least give you some CPU time? Also, make sure you're not implementing a thread's code in any sort of actionEvent or anything weird like that - code running in there doesn't give up control until it is complete or broken out of. Also, as a troubleshooting idea, can you manually interrupt the second thread to continue running the first one? As for socket or networking issues, I can't comment on that, sorry. I haven't gotten that far yet.
-nothing important to say, but learnin' plenty-
You totally ruined the moon. You're gonna hafta pay for that you know. This tiny ad agrees: