I'm working on a huge scale project, and I've stumbled onto something that
appeared to be just random buggy code before we started larger scale testing.
Everytime there is an exception in my code, the session is terminated. I
don't understand why this is. I can't find any reference to it in the
documentation, nor in my google searches so far.
This behaviour is crippling the entire project, I'd really appreciate some
information :(
9  1815 
Would probably need more information, but:
Is the exception safely handled?
Just as an idea, do you think that the session is killing the ASP.Net Worker
process? That would cause the application and therefore the session to
restart.
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:7D**********************************@microsof t.com... I'm working on a huge scale project, and I've stumbled onto something that
appeared to be just random buggy code before we started larger scale
testing.
Everytime there is an exception in my code, the session is terminated. I
don't understand why this is. I can't find any reference to it in the
documentation, nor in my google searches so far.
This behaviour is crippling the entire project, I'd really appreciate some
information :(
When an unhandled exception occurs in an asp.net application the current
session will be terminated and a new one will by default be started. So if
its being triggered by unhandled exceptions you need to implement an
application level exception handler.
Read about a solution here: http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:7D**********************************@microsof t.com... I'm working on a huge scale project, and I've stumbled onto something that
appeared to be just random buggy code before we started larger scale
testing.
Everytime there is an exception in my code, the session is terminated. I
don't understand why this is. I can't find any reference to it in the
documentation, nor in my google searches so far.
This behaviour is crippling the entire project, I'd really appreciate some
information :(
Ok, my exceptions, specifically the ones causing the session to terminate,
are not unhandled. While my exception handling isn't done on
Application_OnError, it is done using a try block.
Also, ~99.9% of my exceptions are being caught by my handlers, so unless
there is something extra I don't know about handling exceptions (quite
possible) then the problem is not an unhandled exception.
My exception handling routines involve placing the stacktrace and message
parts in a RegisterStartupScript block inside a simple javascript alert. This
is done inside a function so that at a later stage I can change it to a
logging mechanism.
Most of my exceptions are caused by database problems, bad sql etc.
Worst of all, I have my boss changing code of mine now because he thinks he
knows what's wrong :/ !!!
"John Timney ( MVP )" wrote: When an unhandled exception occurs in an asp.net application the current
session will be terminated and a new one will by default be started. So if
its being triggered by unhandled exceptions you need to implement an
application level exception handler.
Read about a solution here:
http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:7D**********************************@microsof t.com... I'm working on a huge scale project, and I've stumbled onto something that
appeared to be just random buggy code before we started larger scale
testing.
Everytime there is an exception in my code, the session is terminated. I
don't understand why this is. I can't find any reference to it in the
documentation, nor in my google searches so far.
This behaviour is crippling the entire project, I'd really appreciate some
information :(
For five minutes work try adding an application level handler, specifically
the one in the blog entry........see if it makes a difference.
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:C4**********************************@microsof t.com... Ok, my exceptions, specifically the ones causing the session to terminate,
are not unhandled. While my exception handling isn't done on
Application_OnError, it is done using a try block.
Also, ~99.9% of my exceptions are being caught by my handlers, so unless
there is something extra I don't know about handling exceptions (quite
possible) then the problem is not an unhandled exception.
My exception handling routines involve placing the stacktrace and message
parts in a RegisterStartupScript block inside a simple javascript alert.
This
is done inside a function so that at a later stage I can change it to a
logging mechanism.
Most of my exceptions are caused by database problems, bad sql etc.
Worst of all, I have my boss changing code of mine now because he thinks
he
knows what's wrong :/ !!!
"John Timney ( MVP )" wrote:
When an unhandled exception occurs in an asp.net application the current
session will be terminated and a new one will by default be started. So
if
its being triggered by unhandled exceptions you need to implement an
application level exception handler.
Read about a solution here:
http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:7D**********************************@microsof t.com... > I'm working on a huge scale project, and I've stumbled onto something
> that
> appeared to be just random buggy code before we started larger scale
> testing.
>
> Everytime there is an exception in my code, the session is terminated.
> I
> don't understand why this is. I can't find any reference to it in the
> documentation, nor in my google searches so far.
>
> This behaviour is crippling the entire project, I'd really appreciate
> some
> information :(
No change I'm afraid.
"John Timney ( MVP )" wrote: For five minutes work try adding an application level handler, specifically
the one in the blog entry........see if it makes a difference.
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:C4**********************************@microsof t.com... Ok, my exceptions, specifically the ones causing the session to terminate,
are not unhandled. While my exception handling isn't done on
Application_OnError, it is done using a try block.
Also, ~99.9% of my exceptions are being caught by my handlers, so unless
there is something extra I don't know about handling exceptions (quite
possible) then the problem is not an unhandled exception.
My exception handling routines involve placing the stacktrace and message
parts in a RegisterStartupScript block inside a simple javascript alert.
This
is done inside a function so that at a later stage I can change it to a
logging mechanism.
Most of my exceptions are caused by database problems, bad sql etc.
Worst of all, I have my boss changing code of mine now because he thinks
he
knows what's wrong :/ !!!
"John Timney ( MVP )" wrote:
When an unhandled exception occurs in an asp.net application the current
session will be terminated and a new one will by default be started. So
if
its being triggered by unhandled exceptions you need to implement an
application level exception handler.
Read about a solution here:
http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:7D**********************************@microsof t.com...
> I'm working on a huge scale project, and I've stumbled onto something
> that
> appeared to be just random buggy code before we started larger scale
> testing.
>
> Everytime there is an exception in my code, the session is terminated.
> I
> don't understand why this is. I can't find any reference to it in the
> documentation, nor in my google searches so far.
>
> This behaviour is crippling the entire project, I'd really appreciate
> some
> information :(
Well I'll be... there is an old piece of code in the system logging
exceptions to the bin directory....
"BLiTZWiNG" wrote: No change I'm afraid.
"John Timney ( MVP )" wrote:
For five minutes work try adding an application level handler, specifically
the one in the blog entry........see if it makes a difference.
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:C4**********************************@microsof t.com... Ok, my exceptions, specifically the ones causing the session to terminate,
are not unhandled. While my exception handling isn't done on
Application_OnError, it is done using a try block.
Also, ~99.9% of my exceptions are being caught by my handlers, so unless
there is something extra I don't know about handling exceptions (quite
possible) then the problem is not an unhandled exception.
My exception handling routines involve placing the stacktrace and message
parts in a RegisterStartupScript block inside a simple javascript alert.
This
is done inside a function so that at a later stage I can change it to a
logging mechanism.
Most of my exceptions are caused by database problems, bad sql etc.
Worst of all, I have my boss changing code of mine now because he thinks
he
knows what's wrong :/ !!!
"John Timney ( MVP )" wrote:
> When an unhandled exception occurs in an asp.net application the current
> session will be terminated and a new one will by default be started. So
> if
> its being triggered by unhandled exceptions you need to implement an
> application level exception handler.
>
> Read about a solution here:
>
> http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
>
> --
> Regards
>
> John Timney
> ASP.NET MVP
> Microsoft Regional Director
>
> "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
> news:7D**********************************@microsof t.com...
> > I'm working on a huge scale project, and I've stumbled onto something
> > that
> > appeared to be just random buggy code before we started larger scale
> > testing.
> >
> > Everytime there is an exception in my code, the session is terminated.
> > I
> > don't understand why this is. I can't find any reference to it in the
> > documentation, nor in my google searches so far.
> >
> > This behaviour is crippling the entire project, I'd really appreciate
> > some
> > information :(
>
>
>
does that mean you've solved it before your boss did?
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:BA**********************************@microsof t.com... Well I'll be... there is an old piece of code in the system logging
exceptions to the bin directory....
"BLiTZWiNG" wrote:
No change I'm afraid.
"John Timney ( MVP )" wrote:
> For five minutes work try adding an application level handler,
> specifically
> the one in the blog entry........see if it makes a difference.
>
> --
> Regards
>
> John Timney
> ASP.NET MVP
> Microsoft Regional Director
>
> "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
> news:C4**********************************@microsof t.com...
> > Ok, my exceptions, specifically the ones causing the session to
> > terminate,
> > are not unhandled. While my exception handling isn't done on
> > Application_OnError, it is done using a try block.
> >
> > Also, ~99.9% of my exceptions are being caught by my handlers, so
> > unless
> > there is something extra I don't know about handling exceptions
> > (quite
> > possible) then the problem is not an unhandled exception.
> >
> > My exception handling routines involve placing the stacktrace and
> > message
> > parts in a RegisterStartupScript block inside a simple javascript
> > alert.
> > This
> > is done inside a function so that at a later stage I can change it to
> > a
> > logging mechanism.
> >
> > Most of my exceptions are caused by database problems, bad sql etc.
> >
> > Worst of all, I have my boss changing code of mine now because he
> > thinks
> > he
> > knows what's wrong :/ !!!
> >
> > "John Timney ( MVP )" wrote:
> >
> >> When an unhandled exception occurs in an asp.net application the
> >> current
> >> session will be terminated and a new one will by default be started.
> >> So
> >> if
> >> its being triggered by unhandled exceptions you need to implement an
> >> application level exception handler.
> >>
> >> Read about a solution here:
> >>
> >> http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
> >>
> >> --
> >> Regards
> >>
> >> John Timney
> >> ASP.NET MVP
> >> Microsoft Regional Director
> >>
> >> "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
> >> news:7D**********************************@microsof t.com...
> >> > I'm working on a huge scale project, and I've stumbled onto
> >> > something
> >> > that
> >> > appeared to be just random buggy code before we started larger
> >> > scale
> >> > testing.
> >> >
> >> > Everytime there is an exception in my code, the session is
> >> > terminated.
> >> > I
> >> > don't understand why this is. I can't find any reference to it in
> >> > the
> >> > documentation, nor in my google searches so far.
> >> >
> >> > This behaviour is crippling the entire project, I'd really
> >> > appreciate
> >> > some
> >> > information :(
> >>
> >>
> >>
>
>
>
That it does =) Though that's not too difficult, he only has a basic
knowledge of programming, so he was not likely to solve it anyway... and as
you probably know, that kind of person can be very dangerous when they start
modifying your code....
"John Timney ( MVP )" wrote: does that mean you've solved it before your boss did?
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:BA**********************************@microsof t.com... Well I'll be... there is an old piece of code in the system logging
exceptions to the bin directory....
"BLiTZWiNG" wrote:
No change I'm afraid.
"John Timney ( MVP )" wrote:
> For five minutes work try adding an application level handler,
> specifically
> the one in the blog entry........see if it makes a difference.
>
> --
> Regards
>
> John Timney
> ASP.NET MVP
> Microsoft Regional Director
>
> "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
> news:C4**********************************@microsof t.com...
> > Ok, my exceptions, specifically the ones causing the session to
> > terminate,
> > are not unhandled. While my exception handling isn't done on
> > Application_OnError, it is done using a try block.
> >
> > Also, ~99.9% of my exceptions are being caught by my handlers, so
> > unless
> > there is something extra I don't know about handling exceptions
> > (quite
> > possible) then the problem is not an unhandled exception.
> >
> > My exception handling routines involve placing the stacktrace and
> > message
> > parts in a RegisterStartupScript block inside a simple javascript
> > alert.
> > This
> > is done inside a function so that at a later stage I can change it to
> > a
> > logging mechanism.
> >
> > Most of my exceptions are caused by database problems, bad sql etc.
> >
> > Worst of all, I have my boss changing code of mine now because he
> > thinks
> > he
> > knows what's wrong :/ !!!
> >
> > "John Timney ( MVP )" wrote:
> >
> >> When an unhandled exception occurs in an asp.net application the
> >> current
> >> session will be terminated and a new one will by default be started.
> >> So
> >> if
> >> its being triggered by unhandled exceptions you need to implement an
> >> application level exception handler.
> >>
> >> Read about a solution here:
> >>
> >> http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
> >>
> >> --
> >> Regards
> >>
> >> John Timney
> >> ASP.NET MVP
> >> Microsoft Regional Director
> >>
> >> "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
> >> news:7D**********************************@microsof t.com...
> >> > I'm working on a huge scale project, and I've stumbled onto
> >> > something
> >> > that
> >> > appeared to be just random buggy code before we started larger
> >> > scale
> >> > testing.
> >> >
> >> > Everytime there is an exception in my code, the session is
> >> > terminated.
> >> > I
> >> > don't understand why this is. I can't find any reference to it in
> >> > the
> >> > documentation, nor in my google searches so far.
> >> >
> >> > This behaviour is crippling the entire project, I'd really
> >> > appreciate
> >> > some
> >> > information :(
> >>
> >>
> >>
>
>
>
well I hope I helped, and when his job comes up for renewal let me
know.........lol
--
Regards
John Timney
Microsoft MVP
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:85**********************************@microsof t.com... That it does =) Though that's not too difficult, he only has a basic
knowledge of programming, so he was not likely to solve it anyway... and
as
you probably know, that kind of person can be very dangerous when they
start
modifying your code....
"John Timney ( MVP )" wrote:
does that mean you've solved it before your boss did?
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
news:BA**********************************@microsof t.com... > Well I'll be... there is an old piece of code in the system logging
> exceptions to the bin directory....
>
> "BLiTZWiNG" wrote:
>
>> No change I'm afraid.
>>
>> "John Timney ( MVP )" wrote:
>>
>> > For five minutes work try adding an application level handler,
>> > specifically
>> > the one in the blog entry........see if it makes a difference.
>> >
>> > --
>> > Regards
>> >
>> > John Timney
>> > ASP.NET MVP
>> > Microsoft Regional Director
>> >
>> > "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in message
>> > news:C4**********************************@microsof t.com...
>> > > Ok, my exceptions, specifically the ones causing the session to
>> > > terminate,
>> > > are not unhandled. While my exception handling isn't done on
>> > > Application_OnError, it is done using a try block.
>> > >
>> > > Also, ~99.9% of my exceptions are being caught by my handlers, so
>> > > unless
>> > > there is something extra I don't know about handling exceptions
>> > > (quite
>> > > possible) then the problem is not an unhandled exception.
>> > >
>> > > My exception handling routines involve placing the stacktrace and
>> > > message
>> > > parts in a RegisterStartupScript block inside a simple javascript
>> > > alert.
>> > > This
>> > > is done inside a function so that at a later stage I can change it
>> > > to
>> > > a
>> > > logging mechanism.
>> > >
>> > > Most of my exceptions are caused by database problems, bad sql
>> > > etc.
>> > >
>> > > Worst of all, I have my boss changing code of mine now because he
>> > > thinks
>> > > he
>> > > knows what's wrong :/ !!!
>> > >
>> > > "John Timney ( MVP )" wrote:
>> > >
>> > >> When an unhandled exception occurs in an asp.net application the
>> > >> current
>> > >> session will be terminated and a new one will by default be
>> > >> started.
>> > >> So
>> > >> if
>> > >> its being triggered by unhandled exceptions you need to implement
>> > >> an
>> > >> application level exception handler.
>> > >>
>> > >> Read about a solution here:
>> > >>
>> > >> http://blogs.msdn.com/mattwag/archiv...07/368605.aspx
>> > >>
>> > >> --
>> > >> Regards
>> > >>
>> > >> John Timney
>> > >> ASP.NET MVP
>> > >> Microsoft Regional Director
>> > >>
>> > >> "BLiTZWiNG" <BL*******@discussions.microsoft.com> wrote in
>> > >> message
>> > >> news:7D**********************************@microsof t.com...
>> > >> > I'm working on a huge scale project, and I've stumbled onto
>> > >> > something
>> > >> > that
>> > >> > appeared to be just random buggy code before we started larger
>> > >> > scale
>> > >> > testing.
>> > >> >
>> > >> > Everytime there is an exception in my code, the session is
>> > >> > terminated.
>> > >> > I
>> > >> > don't understand why this is. I can't find any reference to it
>> > >> > in
>> > >> > the
>> > >> > documentation, nor in my google searches so far.
>> > >> >
>> > >> > This behaviour is crippling the entire project, I'd really
>> > >> > appreciate
>> > >> > some
>> > >> > information :(
>> > >>
>> > >>
>> > >>
>> >
>> >
>> >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: yabba |
last post by:
w2k server
as webadmin i have occasion to kill a user session and couse them to login
again. I have the sessionID saved in a file.
is there a way to kill the user session without disturbing...
|
by: drodrig |
last post by:
Hi.
I am trying to close/kill all processes that show visible windows on
Windows XP. So far I've created a script that uses win32gui.EnumWindows
to iterate through all windows, check for which...
|
by: Mangler |
last post by:
I have 2 sessions that get created. One when the user logs in called
"uname" and another called "idrma" when that user choses to begin a
repair request. I know <%session.abandon% will kill both...
|
by: Goofy |
last post by:
Does anyone know how I can kill a session by session ID ?
--
Goofy
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
| |
