Thanks Luc for sharing your knowledgw with us.
Luc Pattyn wrote:
Here are some candidates for large objects: - images - arrays in general - large strings (TextBox/RichTextBox often is a culprit, as it requires the concatenation of all its text) - StringBuillders and all kinds of collections since these typically are implemented as arrays as well; such objects get an initial capacity, and when insufficient, their array gets reallocated with twice the size.
But possibility of above scenarios are not there in case of my window service. In my case , i am calling a web service which puts the message in the IBM MQ.Exception comes whenever i attemp to call the web service method. (1)One possible cause for exception might be that the message size is very big :confused:... waiting for your views on that (2)Also, is it possible to monitor the memory used be window service(something with performance counter or some other way) ??? (3)For immediate solution should i restart my production server or restarting of window service do the trick...
himanshu