Shared objects of Singelton class for different webmethod calls of a webservice
I am running a webservice in production and this webservice uses a library and all classes in that library are singleton. I am not using locking mechanism there in singelton calls.
When I try to call a webmethod from multiple instances of an application i face concurency issues as the dataset seems to be shared for different calls.
I thought that by definition webservices are using HTTP and thus they are stateless and the objects will not be shared among different calls from different applications. But it doesnt work as expected. Can you please guide me if there is any setting (pooling) which can be turned off so that objects are not shared among different calls to same web methos.