Evidence of Resource Leak?

Rod Widdowson rdw at steadingsoftware.com
Tue Feb 10 12:52:31 EST 2015


> Yes. I'm actively working on testing Rod's changes in IDP-592, so I'll follow up 
> here w/r/t the resource leak and on the issue once I get a working resolver config

The intention is that the IDP-592 fix plug that resource leak.

When I read your post my immediate assumption was that the springResource thing was causing the leak, however my instinct is that the memory will only be leaked on every successful resolver reload which should only happen if the resources are changing.  I guess that if you were working of getting the configuration right there would have been plenty of reloads. 

On the other hand it seems strange that it consumed memory over the weekend while you were not working so I'll make a note to check to make sure that we are not reloading too frequently.  Equally, if you have suitable logs could you check to see whether the AttributeResolver Service was reloading configuration all weekend?

Thanks

/Rod



More information about the dev mailing list