A customer has a home grown .net 4.0 "search service" that gets called from an IIS/AppPool using .Net remoting. So the communication goes as follows:
Frontend Tier - IIS - .Net App Pool - Search Service
When the Search Service is started with an agent it no longer gives feedback of search results. Some investigation and restarts later it turns out that the culprit is the .Net Remoting sensor. When we disable it the application works as expected.
Can you shed some light as to what this sensor does? I cannot find anything in the documentation.
did you figure if it was actually the ".NET Remoting" or ".NET Remoting Tagging" Sensor (the latter can only be unplaced separately in debug mode)?
this is what they do:
figuring out which one of those two would be interesting anyway, but I suggest opening a support ticket in any case.
just wondering: the search service is really up and running and not maybe running into a timeout due to slow instrumentation or something like that?
Thanks for the reply.
I did not specifically unplace the .Net Remote Tagging sensor. Does it get unplaced together with the .Net Remoting sensor?
We left the search service starting for roughly 10 mins, I doubt it would still be instrumenting.
I will work with the customer tomorrow to figure some more things out and will then also create a support ticket.