Lost logged in users

Hi there,</o>

We have a Web Application which takes data from a database and creates reports for the current user. After the reports created in memory we merge theses reports to a single PDF file and send it to our user.</o>
</o>
Our problem isafter creating the single PDF file our Web Application ?loses? the logged in user. Sometimes the reports are not generated and the logged in user always ?disappears?. The report generation takes 7-9 seconds.

After browsing this Forum I had the idea may be we exceed either the 75% CPU time or 100 MB memory limit or both during report generation and our application was automatically recycled. (I did not know this "rules") I contacted the Customer Service and they confirmed that they found the signs of a lot of recycling in the log file of our Web Application during the last few days. They could not tell me whether the recyclings were caused by exceeding CPU or Memory limit. They also suggested to post this story to this Forum may be somebody can help.
</o>
So what I need ? I guess ? is some software tools which should help to decide what causes the app recycling and where in the code. Can anybody help?</o>
</o>
Thanks in advance,</o>
Louis</o>
</o>

 

This is something that does happen even in production Lan environments.
All of us have access to something now that I would have used for this in the past...Linq

Have you considered writing to an XML file during the process?
Would take some experimentation but I can imagine where it would be a great fallback plan.
Just a suggestion.
All the best,
Mark

P.S. Some great Linq learning videoswere added to http://asp.net recently.

 

Hi Mark,


Thanks for the XML/Linq suggestion. Both might work but for the Linq we have to upgrade to VS2008 and Win Server 2008/IIS7.
Saving reports to XML and merge them form the saved files might decrease the memory usage. I will try it.


Thanks,
Louis

 

You can also use Linq to XML here on IIS6 with .NET 3.5, I was doing it.
Have now migrated to IIS7 but I did have Linq to XML working already, and it was blazing fast.
Salute,
Mark

 

No, unfortunatelly we have VS2005, .NET2.0, Win Server 2003 and IIS6.0.
For Linq we do need the .NET3.5 and VS2008 I think?
Thanks, Louis

 

The .NET 3.5 web.config changes are not part of VS2005 but you can use VS2005, just harder to code.
You can also use the free VDW2008 with VS2005.
Salute,
Mark

 

Thanks, I will try it.