User Profile & Activity

Eric Member
Page
of 19
Posted: March 25, 2011 4:43 AM

Hi Handy,

If you have a documentation, then I have never seen it. And I also cannot find it. On your old website there were a few articles, but they are gone now. On my PC there is no documentation and I installed the full WebUI.Studio (although I only need the WebGrid). On your website I also cannot find a documentation. I found a chm file for download, but that doesn't run on a network drive (desktop) and if copied to some local drive (I'm an admin, so I can do that) I can see that it only contains framework documentation. I never saw a document describing all events and properties etc. of WebGrid. If I cannot find it, then probably many other users have the same problem. This is something your company should work on. Please provide me with a link to your mentioned document "Event sequence".

But even if I would find the document "event sequence", does it say that I am not allowed to do data binding in Page_Load event?

Please note that all this code was not written by me. I don't want to rewrite big progams of other people that left the company. I just want to fix the problems. And crashing is a big problem.

Also, please note that this crash happens on all pages that use the WebGrid. One of the pages that crash were written completely new with your help and don't do data binding in Page_Load event (but contain several grids and use complicated events and mutual updates on both client and server side). I didn't want to send you that page, just because it's too complicated and preferred a simple page.

Can I assume that you are still investigating the root cause?

Thanks,

Eric

Posted: March 24, 2011 2:29 PM

Hi Handy,

I don't see what you want to tell me. Does this mean that crashing once a month is "normal" if we use binding in Page_Load event? I hope not. We also won't change the implementation and make a new release of our application just to try out if it might happen less frequently or go away with a new code design.

In any case there is some weird bug in WebGrid and I would like to get this solved somehow.

Thanks,

Eric

Posted: March 24, 2011 7:50 AM

Hi Handy,

This is by design. Maybe there are other ways to implement this. But I think you don't want to start a discussion on the implementation design here, right? We are talking about a server crash once a month caused by WebGrid.

Thanks,

Eric

Posted: March 24, 2011 5:37 AM

any update yet?

Hi Handy,

If you will fix it, no matter in what version, then there is no reason to be sorry.

Please update this thread when it is fixed.

Thanks,

Eric

So the crash in the initial sample will get fixed (in WebGrid 7)? Or has to get approved to get fixed by management first? Or how will this go on?

Eric

Posted: March 17, 2011 6:31 AM

Hi Handy,

No, I don't get an error message. The OnUnhandledError client-side event gets triggered as mentioned above. Maybe if it would not be handled then this communication error would appear instead.

What I do know already is that at that time the server was NOT under heavy load. I don't know the memory condition though. But the fact that only WebGrid is affected is quite strange.

Also, restarting the WebServices (IIS) does not help, only rebooting the server.

Regards,

Eric

Hi Handy,

Please note that this problem is not related to WebGrid6. You never said the crash is fixed in WebGrid7, only the slider bug is solved in WebGrid7. So I don't expect any bugfixes in WebGrid6. But I don't see any reason to upgrade to WebGid7 if it has the same bugs. And as far as I remember you could even reproduce the bug with WebGrid7.

So we are talking about a crash in WebGrid here. Either you can provide a useful workaround or you should fix the bug. It is true that you suggested one workaround and I provided various samples to demonstrate you that this workaround doesn't work.

You tried to change the whole structure of the events. Maybe because you usually implement it this way. With this structure change, it is now required to have all database data ready where we usually don't have the data yet. We cannot have two database calls just to fill the grid. This not only doesn't work for performance reasons, but also could yield different results if the database changes between the two calls - as I showed you in a sample.

In your last post from February 21 you told me you understand the problem and want to find a way with the developers on how to implement this. Since then I didn't hear any new answer from you. I think we're not doing anything unusual, so it shouldn't be so complicated.

So can you fix this bug or provide a useful workaround or not?

Thanks,

Eric

Posted: March 16, 2011 5:21 AM

Hi Handy

My attachment was included with my email. I received a receipt-confirmation and a ticket number [IS-B7377DC1-838C-4E46-A2A2-AC67D615C169] {96804}

Please look at the ZIP file called crash2.zip in there. There is a subfolder in the ZIP called crashlog_cleartext with seven text files in it. Let me know if you still cannot find it.

Thanks,

Eric

 

Posted: March 15, 2011 10:06 AM

Hi Handy,

I've sent you the code. Here's a copy of my email (without the attachment), as reference.

Eric

---

Hello,

As requested in
http://www.intersoftpt.com/Community/WebGrid/WebGrid-server-crash-every-month/ I can send you here the code.

I replaced some keywords to single-letter abbreviations etc. and removed connection strings etc. (marked with [removed]), but otherwise left everything as it is. I only included one page that crashes. Please note that there is no problem in the code, the page works fine in normal cases. Only when the special server condition occurs, then I don't get a response and the WebGrid immediately runs the OnUnhandledError client-side event. Here this just shows a JavaScript dialog, but on other pages it redirects to a general error message page.

I also included a log of the HTTP protocol that happened at that time. You can see the q (requests) 1..3 and r (responses) 1...3 in raw in the crashlog_cleartext folder. Request 1 and 2 are the page load and request 3 is when the user expands a node. As you can see, the response is empty, which triggers the client-side error handler.

The sourcecode only contains the problematic page with some additional files needed. The two javascript files contain only the function that gets called. Actually you won't be able to compile it, but with this info you should be able to see what happens on that page.

Let me know if you need any specific additional infos. But please don't try to let me change the code to see if this would solve the problem. It works fine in normal cases, so there must be a specific condition (maybe server overload, memory low, or anything else) on the server that results in a condition where the server just returns nothing, but for other requests (unrelated to WebGrid) everything works fine then. So it must be related to WebGrid.

Regards

Eric
All times are GMT -5. The time now is 11:00 AM.
Previous Next