Getting this error in my App…
This link suggests that i change:
foreach(Subscriber s in subscribers)
foreach(Subscriber s in subscribers.ToList())
.toList() will return a new list. But note that this is a list of subscribers, which is a ref type and so the new list ref will also point to the old objects only…
But this error will not come as now when the old list of subscribers has an object added or removed, the subscribers.ToList() list will not change and hence this exception will not be thrown….
Clearly this is not something that I want, as I need to make sure the list being iterated is not being modified at the same time..this is a design issue with my app….so thought .toList will avoid this error, it will still not solve the problem at all….
When a function is called, a copy of it is put on the Stack to execute. When a
function exits, it is pulled from the Stack. If it calls other functions,
these are stacked on top of it, and each one is pulled off the Stack when it
The Stack Trace shows the “topmost” (latest) functions called. It helps
identify the chain of execution that led up to the current situation
(usually an exception). It identifies each function on the Stack in the
order (reversed) in which they appear, with the last one executed at the
Card1 (the first card on the discard pile) calls 2
which calls 3. You cannot finish working with card 1 until you have played
card 2 and card 3 (and so on). This would be like function Card1() calling
function Card2(), which calls function Card3. If you break inside the
Card3() function, you have a stack like so:
Now, let’s say Card3 returns an answer that Card2 processes, and Card2 has
an error. The stack now looks like so:
In the stack trace, you will see Card2 with a line number and Card1 with a
line number, if you have the IDE set to break on all errors, or if you let
the error remain when deployed and do not have a Try … Catch to handle the
Sometimes what you do in your code does not throw an exception until it hits
the .NET Framework components. In these cases, you often have to look down
the stack until you hit your own functions to determine what actually caused
Issue: After a certain no. of open http connections to the service, the clients are not able to connect and the app pool recycles.
Interesting IIS Properties to look at:
- Max Concurrent Connections (maxConnections)
- Connection Time-Out (connectionTimeout)
Use this link as reference: http://www.iis.net/configreference/system.applicationhost/sites/site/limits
Also, Dynamic IP Restrictions Module is used to limit connections from the same machine. The limit can be changed in the module’s details page in IIS Manager.
In order to BIND the indexing by Splunk of your CUSTOM Logs, a new “stanza” must be added by editing the props.conf file.
Once a non-system log is associated it with a sourcetype and is “recognized” in this file, Splunk will index and display.
Edit the props.conf file over at $SPLUNK_HOME/etc/system/local/ or in your own custom application directory in $SPLUNK_HOME/etc/apps/.
The admin must only modify at one of these two locations.
Optionally, you can add this stanza from the Advanced Mode tab in data preview from the UI.