Hi,
> MorganStanley.spg.crms.ajax.AjaxHandler
you know that I'm not very happy to see this... :(
You need for each type a ashx file, so this is not working as simple
as you think. Maybe I have time to look at this if it is possible to
run it without the httpHandler section in web.config.
Regards,
Michael
On 6/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Actually, I'm starting to zero in on the problem a bit more. Our Ajax
> calls are receiving NullReferenceExceptions quite randomly. I've put
> some more logging into our app to investigate and it seems that we have
> the null reference thrown from
> AjaxPro.ConverterJavaScriptHandler.ProcessRequest():
>
> Error spg/cvrms System.NullReferenceException: Object reference not set
> to an instance of an object.
> at AjaxPro.ConverterJavaScriptHandler.ProcessRequest(HttpContext
> context)
> at
> MorganStanley.spg.crms.ajax.AjaxHandler.ProcessRequest(HttpContext
> context_) in c:\jason\cvrms\trunkdev\spg\crms\dev\crmslib\<client name
> omitted!>\spg\crms\ajax\ajaxhandler.cs:line 25
> at
> System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
> at System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
> Boolean& completedSynchronously) (noclass.)
>
> As I'd mentioned, we had to do some trickery to get Ajax to work
> because restrictions in force on our hosting environment. We are not
> allowed to define HttpHandlers in our application's web.config file (as
> they are set to "machineOnly" in the machine.config). Instead we
> create a dummy .ashx file with the following contents:
>
> <%@ WebHandler Language="C#" Class="Ajax.AjaxHandler" %>
>
> This file gets named the same as the request (such as core.ashx), so
> when the server sees it, it gets compiled and the webhandler definition
> tells it to pass the request to a custom implementation of IHttpHandler
> that we've defined. That has the following ProcessRequest()
> implementation:
>
> public void ProcessRequest(HttpContext context_)
> {
> AjaxHandlerFactory factory = new AjaxHandlerFactory();
> IHttpHandler handler =
> factory.GetHandler(context_,
> context_.Request.RequestType,
> context_.Request.RawUrl,
> context_.Request.PhysicalApplicationPath);
> handler.ProcessRequest(context_);
> factory.ReleaseHandler(handler);
> }
>
> I don't know if this workaround if truly relevant to the error we are
> seeing but I wanted you to be aware of what we are dealing with. This
> setup has been working fine under a load of 200 users for 4 months, and
> just last week it started popping up with the null references. BTW, we
> are using v 5.11.24.1 of the AjaxPro.dll. Has anyone ever reported
> seeing something like this? Again, it doesn't seem to be related to
> any new piece of code that we wrote.
>
> Thank Michael, if you are aware of anything, any info is greatly
> appreciated.
>
> Regards,
> Jason
>
>
> >
>
--
Best regards | Schöne Grüße
Michael
Microsoft MVP - Most Valuable Professional
Microsoft MCAD - Certified Application Developer
http://weblogs.asp.net/mschwarz/
http://www.schwarz-interactive.de/
mailto:[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ajax.NET Professional" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/ajaxpro
The latest downloads of Ajax.NET Professional can be found at
http://www.ajaxpro.info
-~----------~----~----~----~------~----~------~--~---
