We have been using Infragistics 2006v1 for a few years without any issues. We recently renewed and updated our site to Infragistics 2009v2. After a day or so of uptime on our production server we start getting random exceptions with the infragistics controls. The exact exception that start it off is below. The only way to fix this is to do an IIS reset and then it will be stable for a day or so.
** Exception : Object reference not set to an instance of an object.
** Stack Trace : at
Infragistics.WebUI.Shared.GlobalCssHelper.GetPageContainer(Page page, Boolean create)
at Infragistics.WebUI.Shared.GlobalCssHelper.OnInit(WebControl
control, Page page)
at Infragistics.WebUI.WebDataInput.WebTextEdit.OnPreRender(EventArgs
e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Hi Chris,
Thank you for a report.That issue was introduced around 7-8 months ago due to work around memory leaks on server which occurred in some specific applications. Around 2 months ago, that was reviewed and current version uses different logic. Particularly the GlobalCssHelper class which was used in earlier versions before AppStyling, was deprecated and removed from logic.
Please get latest service release, it should not have that issue.
I checked source codes and found that that fix did not go to the RELEASE build yet. I hope, that will be available in coming service releases.
We have a very large government customer who experienced this issue. We are going to upgrade the the fixed version. However I have been asked to verify it in the code. The Problem and the Fix. Can you tell me what caused the problem and show me what the fix is.
Thanks Gary
Hi Gary,
That issue was introduced after attempt to fix a minor issue, reported around 8-9 months ago, for unreleased memory on server. That "fix" included validation for not disposed objects (used by css-architecture) and disposing them when they were not needed. A side effect, which happened when several requests hit server from different threads, led to null reference exception. That was hard to catch and it was never reproduced on local servers.
That regression issue was reported in a month after "fixed" version was released. Once it was reported, the architecture of css was modified and classes which used static objects were removed.
The only option to fix- is to upgrade to newer version or to return to verion which was release around a year ago.
Hi Viktor
Thanks for your detailed response. However, since we have the source code could you point to the area that actually fixed the problem?
Gary
2 files in shared dll were modified: RenderBase.cs and ClientScript.cs.
It is better to get latest service release. Though, If you prefer to have those files, then please give me your email, so, I can send those files.
Thanks Viktor
We have the latest release we just need to install it. I was asked to verify the fix for our client. I think your first answer plus this is fine.
Thanks
Yes
Hi Viktor ,
Is this issue been taken care of in NetAdvantage for Web Client 2009 Vol. 2 - ASP.NET Service Release (20092.2099).
I am having similar problem. I have the latest Netadvantage 2009 V2. Works fine on test but on production server 2003 SBS, this started afte ri upgraded to 2009 V2 on .NET 2.0
Thanks for the help...
Hi Jamie,
Yes. Fixes are applied for all (old and new) versions.
Hey Viktor,
Does the release of 2010 Vol1 contain the fix as well?
Thanks,
Jamie