1
Vote

Object '/xxx/xxx.rem' has been disconnected or does not exist at the server error if the command line runs too long

description

Noticed this error if one runs the command line with a file fed to it full with commands (using the @filename command). It has to do with the whole process running too long as with fewer commands there is no error anymore. The error seems to surface from index rebuild commands.

Apparently such errors are caused by the GC running too early and can be circumvented.

file attachments

comments

sebastienros wrote Oct 29, 2013 at 8:25 PM

Please provide a repro

Piedone wrote Oct 29, 2013 at 10:26 PM

This is the command list that is executed (i.e. Orchard.exe @PathToCommand.txt):
feature disable Orchard.OutputCache /t:Default
feature disable Orchard.Warmup /t:Default
feature disable Piedone.Combinator /t:Default
feature disable Orchard.OutputCache /t:Tenant1
feature disable Orchard.Warmup /t:Tenant1
feature disable Piedone.Combinator /t:Tenant1
feature disable Orchard.OutputCache /t:Tenant2
feature disable Orchard.Warmup /t:Tenant2
feature disable Piedone.Combinator /t:Tenant2
feature disable Orchard.OutputCache /t:Tenant2
feature disable Orchard.Warmup /t:Tenant2Eng
feature disable Piedone.Combinator /t:Tenant2
feature disable Orchard.OutputCache /t:Tenant3
feature disable Orchard.Warmup /t:Tenant3
feature disable Piedone.Combinator /t:Tenant3
feature disable Orchard.OutputCache /t:Tenant4
feature disable Orchard.Warmup /t:Tenant4
feature disable Piedone.Combinator /t:Tenant4
What happens is demonstrated on the screenshot. The error is raised after the command feature disable Orchard.Warmup /t:Tenant2 is run.

AimOrchard wrote Oct 30, 2013 at 7:28 AM

I saw this in the past with one of our long running commands.