Click here to Skip to main content
16,012,316 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I have looked at similar articles on this topic without actually getting a solution to the problem i'm facing.

I have a c# web service that contains two threads and they all start and work perfectly when tested on the ASP.NET development server on my development machine, which might suggest that the code is in order.

Since I intend to deploy it on IIS 7.5, I decided to test it on a local copy of IIS 7.5 on my development machine. On IIS, I noticed that the threads refuse to start. Before I resorted to using threads, I have used System.Timers Timer, and System.Threading Timer with the same behaviour, that is, the Timers worked on my ASP.NET development server but refused to work when tested on IIS. Please, What could be the reason for this and what do I do to solve this bottleneck.

Thanks so much for your contributions.
Posted
Comments
ZurdoDev 30-Jul-13 16:58pm    
I don't know but I would suggest posting some relevant code or else you are just hoping that someone else who has had the same exact problem reads this.

Why are you using threads in webservice anyway?

1 solution

I just learnt the hard way that I wasn't supposed to use threads in the web service. After removing the threads, it still worked fine.
 
Share this answer
 

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900