losing sessions when running in StateServer mode
in [ASP .NET]
|
Prev: System.Web.IHttpHandler, System.Web.SessionState.IRequiresSess
Next: Looking for a NNTP server that discuss csharp/.net
From: 3P on 23 Jul 2010 13:11 Dnia 23-07-2010 o 18:54:18 Mr. Arnold <MR. <Arnold(a)arnold.com> napisa�(a): > > "3P" <nospam(a)serwer.pl> wrote in message news:op.vgaq2aulmsp0fz(a)mcs... >> >> Now I know for sure. You are plain dumb. I kindly asked and You are >> attacking me. > > I am not here to hold your hand nor did you work on the project. Those > are the facts that can't be ignored. > What are you talking about? I don't understand you. > > >> And BTW this is very ugly solution. You don't know a lot about ASP.NET >> as You shown in this thread. > > Yeah right!!!!!! And I am sure you no nothing about OOP, ASP.NET WCF Web > services and ADO.NET Entity Framework used in n-tier technology. :) And You know their names only. I know more then you will ever learn. I bet your code is ugly as hell and totally unreadable. You know nothing about designining, TDD, refactoring, CC, MC and other code stats. Show us one of your "Enterprise apps" that are "not high usage". LOL. Yeah this is enterprise app. No one is using it but it is enterprise. This is not the first thread where you talk when You have nothing clever to add.
From: 3P on 23 Jul 2010 13:12 Dnia 23-07-2010 o 19:00:04 Mr. Arnold <MR. <Arnold(a)arnold.com> napisa�(a): > > "3P" <nospam(a)serwer.pl> wrote in message news:op.vgauvgshmsp0fz(a)mcs... >> >>>> SQL Server state is a whole lot slower. Never used it myself. >>> >>> I have used it in a couple of shops. It was OK, and I didn't really >>> see any performance issues using a SQL State server. >>>> >>>> If you had been following the thread closely you will have seen that >>>> the problem turns out to be that the session-id is being lost. >>>> (Session-id is not itself stored in the session.) If the session-id >>>> is being lost then this will affect any session regardless of the >>>> mechanism used to main it (in-proc, state or sql server). If you can >>>> suggest how the OP might investigate the cause of this then that >>>> would be helpful. >>> >> Because that was small app. It is a lot slower. And it doesn't scale >> well. MS words >> if You don't believe me. > > Here you go projecting again I see. >> >> You can make it work a bit faster if You turn off session on pages that >> doesn't need it or set read only session access mode. > > Like all pages need session? > What? Learn english idiot. >> On large app You will probably have to write >> custom code and use many session databases on many servers. > > I don't believe you. So read the books muppet. I don't know where You get your knowledge from.
From: "Mr. Arnold" MR. on 23 Jul 2010 13:34 "3P" <nospam(a)serwer.pl> wrote in message news:op.vgaubq1qmsp0fz(a)mcs... >> It was an async thread with no return. So the pages were not waiting >> for a return, which was using an async WCF Web service on the back-end, >> a Web service farm. There were no performance issues. The main point was >> to get the object back into session if it was lost -- no matter what >> caused the session to be lost with IIS resets being done 5 to 6 times >> throughout the day, which was used worldwide 24/7. It was a critical >> application within the enterprise level solution, but it was not a high >> usage application within the total enterprise solution. > > Well every thread is async. > > I know page wasn't waiting for thread to finish, but still two worker > threads > were used for every page load/unload. But You said it wasn't high usage > app. That's > probably why You didn't see performance penalty. Oh and one other thing here, the Page-Unload was calling the Page_Unload method in the Presenter of a Model View Presenter using object injection. It was the Presenter that was serializing the object, spawning the async thread and calling the async ASP.NET WCF Web service. The UI was a dumb UI with no code behind it other than to call the methods on the Presenter and pass objects in the View Interface. As a matter of fact, it was the Presenter that was controlling and using the session object in the Presenter and not the Web Page. It was the Presenter that was manipulating the Web controls in the Presenter via the View Interface for the Web page.
From: "Mr. Arnold" MR. on 23 Jul 2010 13:43 "3P" <nospam(a)serwer.pl> wrote in message news:op.vga3ews1msp0fz(a)mcs... <snipped> I don't have time for a trolling clown such as yourself.
From: "Mr. Arnold" MR. on 23 Jul 2010 13:42
"3P" <nospam(a)serwer.pl> wrote in message news:op.vga3cmpzmsp0fz(a)mcs... > Dnia 23-07-2010 o 18:54:18 Mr. Arnold <MR. <Arnold(a)arnold.com> napisa�(a): > >> >> "3P" <nospam(a)serwer.pl> wrote in message news:op.vgaq2aulmsp0fz(a)mcs... >>> >>> Now I know for sure. You are plain dumb. I kindly asked and You are >>> attacking me. >> >> I am not here to hold your hand nor did you work on the project. Those >> are the facts that can't be ignored. >> > What are you talking about? I don't understand you. > >> > >>> And BTW this is very ugly solution. You don't know a lot about ASP.NET >>> as You shown in this thread. >> >> Yeah right!!!!!! And I am sure you no nothing about OOP, ASP.NET WCF Web >> services and ADO.NET Entity Framework used in n-tier technology. :) > > And You know their names only. I know more then you will ever learn. > I bet your code is ugly as hell and totally unreadable. You know nothing > about > designining, TDD, refactoring, CC, MC and other code stats. Show us one of > your > "Enterprise apps" that are "not high usage". LOL. Yeah this is enterprise > app. > No one is using it but it is enterprise. This is not the first thread > where you > talk when You have nothing clever to add. You clown, I have used every last bit of it MBunit, Gallio, and and Reshaper in TDD. You are a clown, the continues to project when you don't know jack about anyone's situation. And in my 38+ plus years in being in it with over 30 of them being in programming, I have for sure forgotten more than you'll ever know. You couldn't hold a match stick to my long and illustrious career in IT. |