Exception while #flushCacheSoon

Chris Muller asqueaker at gmail.com
Wed Dec 5 02:31:52 UTC 2007


Magma never calls MagmaSession>>cleanUp itself.  If your Seaside
framework is calling that during an image save then that is almost
certainly your problem.

Other than that, I have no idea.  Send me scripts and a step-by-step
procedure to reproduce the Exception in a Magma-only image (without
Seaside).  If you do that I'm sure we'll get straight to the bottom of
it.



On Dec 4, 2007 6:28 AM, Sebastian Sastre <ssastre at seaswork.com> wrote:
> Hi Chris, all,
>
>         I've seen, by now 4 or 5 times, an exception while Magma is in the
> middle of a #flushCacheSoon. I don't know the causes yet but I guess is
> because the image is in development and when I save it is stoping and
> restarting everything (Magma server, Seasdide, etc) also noticeable is that
> when stoping Magma it performs some housekeeping like calling
> MagmaSession>>cleanUp.
>
>         The exceptions I saw seemed to happen when a new session try to use
> repository. I close the debugger and the applications just goes normal.
>
>         Any suggestion? I can try to send you more info about this next time
> I catch one.
>
>         cheers,
>
> Sebastian Sastre
>
>
>
> _______________________________________________
> Magma mailing list
> Magma at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/magma
>


More information about the Magma mailing list