[mapguide][MG201][Modified] Exception handlers in proxy code do no catch access violatio...

[Trevor Wekel]

You can view the artifact detail at the following URL:

    https://mapguide.osgeo.org/servlets/Scarab/id/MG201

Type:
Defect

Artifact ID:
MG201 (Exception handlers in proxy code do no catch access violation exception)

Modified by:
Trevor Wekel
trevorwekel (trevor.wekel at autodesk.com)

The following modifications were made to this artifact:
---------------------------------------------------------------------

-- Review Comments set to new value:
Trevor
------
This is a good first step.

C Runtime exceptions like invalid memory access need to be handled with caution.  Ideally, we should try to unwind the stack using our standard catch mechanism to give us information on where the error occured.  Then we should force an orderly shutdown and restart of the application if possible.

Futher investigation should be performed on "orderly shutdown" of the .Net API, Java API (Tomcat), FastCGI mapagent and mgserver.




---------------------------------------------------------------------
This message was automatically generated by Project Tracker.