Maestro 2.0 live dvd fixes

[jng]

2 tickets reported from the OSGeo Live DVD

MapGuide Maestro gets CPU usage to 100%

​http://trac.osgeo.org/osgeo/ticket/699

MapGuide Maestro port fix

​http://trac.osgeo.org/osgeo/ticket/687

The fix for 687 is an easy one (a patch is attached made against the MAESTRO-2.0 tag)

The fix for 699 requires more investigation (I'm currently downloading the v4.5RC1 vm image). I may not find a sufficient solution before the March 14 build/release date

[jng]

Default site url patch for Maestro on OSGeo Live DVD

[jng]

The CPU usage is most likely due to the limited thread pool size in Mono's implementation

See: ​http://www.mono-project.com/ThreadPool_DeadLocks

I fired up a shell on the Live DVD and ran:

export MONO_THREADS_PER_CPU=2000

and then

mono Maestro.exe

Upon exiting, the 100% CPU usage was no longer observable and top does not show zombie mono processes eating up the CPU.

So the solution would be to modify the shortcut to export MONO_THREADS_PER_CPU=2000

[jng]

100% cpu fix

[jng]

assembly version patch

[jng]

The other definite cause of the 100% CPU was due to Maestro attempting to close down the main form as it is loading (which it will do if the user cancels the login dialog).

While this is fine on Microsoft's .net framework, on Mono it obviously has problems with this approach resulting in a zombie mono process on linux. The attached patch prompts for login first, and only when the user logs in will it then start showing the main form.