Maestro crash when restorign large packageo (MGOS 2.2 RC1)

[andrewd]

I keep getting the following crash when I restore a large package. This is using MGOS 2.2 RC1 (happens with both x64 and x86). The package restores fine - the crash just happens while waiting to hear from the server. Rather trivial - but a crash that's consistent..

See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.

Exception Text System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.

at OSGeo.MapGuide.MaestroAPI.PackageBuilder.PackageProgress.backgroundWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)

Loaded Assemblies mscorlib

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900) CodeBase: ​file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

---

Maestro

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/Maestro.exe

---

OSGeo.MapGuide.Maestro.LoginForm

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.Maestro.LoginForm.DLL

---

System.Windows.Forms

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

---

System

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

System.Drawing

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

---

System.Xml

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

---

System.Configuration

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

---

onjcijhf

Assembly Version: 2.1.4.5245 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

OSGeo.MapGuide.Maestro.MaestroEditorInterface

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.Maestro.MaestroEditorInterface.DLL

---

OSGeo.MapGuide.MaestroAPI

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.MaestroAPI.DLL

---

OSGeo.MapGuide.Maestro.ResourceBrowser

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.Maestro.ResourceBrowser.DLL

---

OSGeo.MapGuide.Maestro.ResourceValidators

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.Maestro.ResourceValidators.DLL

---

System.Data

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

---

System.Web

Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4955 (win7RTMGDR.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll

---

Microsoft.JScript

Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.4927 CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/Microsoft.JScript/8.0.0.0__b03f5f7f11d50a3a/Microsoft.JScript.dll

---

pnzwpowq

Assembly Version: 2.1.4.5245 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

i-vb-uhe

Assembly Version: 2.1.4.5245 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

OSGeo.MapGuide.Maestro.ResourceEditors

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.Maestro.ResourceEditors.DLL

---

OSGeo.MapGuide.Maestro.FusionEditor

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.Maestro.FusionEditor.DLL

---

zmkobt_p

Assembly Version: 2.1.4.5245 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

OSGeo.MapGuide.MaestroAPI.PackageBuilder

Assembly Version: 2.1.4.5245 Win32 Version: 2.1.4.5245 CodeBase: ​file:///C:/Program%20Files%20(x86)/OSGeo/MapGuideMaestro/OSGeo.MapGuide.MaestroAPI.PackageBuilder.DLL

---

2dv4z5tl

Assembly Version: 2.1.4.5245 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: ​file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

JIT Debugging To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

[jng]

Retargeting to 3.0. If you are a 3.0 tester, see if this ticket is still relevant

[jng]

Marking as invalid due to ticket inactivity and that large package loading should really be done via the Site Administrator.

[andrewd]

If large package loading should really be done via the Site Administrator, then Maestro shouldn't claim to be able to do it - ie, it should either give a warning that it may/will not work, or you should remove the capability of working with packages. Just a suggestion...I'll resubmit the ticket if I happen to run into it again, anyway.

[jng]

The package loading is nothing more than calling an exposed APPLYRESOURCEPACKAGE mapagent operation. I make no claims about the capabilities of this operation.

I do not consider loading large packages (several hundred MBs in size) to be a common enough scenario to warrant my attention. IMO, if your package grows to this size, it's time to start considering aliases, instead of feature sources with embedded data.

[andrewd]

My package wasn't several hundreds of Mb. It was just a shade over 100Mb...What I was doing in this case was to make a complete backup of one server's library, and then copying it to a 2nd server. That seems like a perfectly logical use for packages.

I realize that you make no claims about any capabilities - that's fine. I realize it's just a gui...I'm just saying that I was an average user that used the tool and got a crash. All I meant was that I will repost it as a bug if v3 still has it...and if it still does, then that new ticket should remain open until it's fixed (I thought that was the point of the "priority" field in the ticket).