Sharepoint Issues after an Application Pool Recycle
My site is setup to use SharePoint 2010's automated Application Pool Recycling. I have 2 front end web servers.

Sometimes (not everytime) the application pool recycles, and a custom webpart starts to display "Object reference not set to an instance of an object." This only happens on 1 of the front end servers, not both. Also, it is not always the same front end server. Furthermore it isn't always the same webpart.

I error handle the webparts, so the site/page still comes up. The webpart just doesn't appear. The SharePoint logs only mention "Object reference..."

If I recycle the application pool again everything returns to normal (the webpart starts working as normal).

Are there issues with SharePoint's automated app pool recycling? Anything I might want to try to relieve this issue?
Sharepoint Issues after an Application Pool Recycle
===

My site is setup to use SharePoint 2010's automated Application Pool Recycling. I have 2 front end web servers.

Sometimes (not everytime) the application pool recycles, and a custom webpart starts to display "Object reference not set to an instance of an object." This only happens on 1 of the front end servers, not both. Also, it is not always the same front end server. Furthermore it isn't always the same webpart.

I error handle the webparts, so the site/page still comes up. The webpart just doesn't appear. The SharePoint logs only mention "Object reference..."

If I recycle the application pool again everything returns to normal (the webpart starts working as normal).

Are there issues with SharePoint's automated app pool recycling? Anything I might want to try to relieve this issue?