We're having some session issues with Chameleon, and from reading other postings recently, others have too.<br><ol><li>Different Chameleon sessions running simultaneously are now and them (1/100 probability) trying to remove files that are being removed by another session. So there are conflicts in the log file.
</li><li>I've noticed after a recent debug run on sessions that the destroy function never runs!!</li></ol>Our systems guy has asked if we can just use a shell script - and that's fine for now, and for us, but it's not a Chameleon resolution. I'll have to disable the garbage collection whenever I upgrade.
<br><br>Also... does anyone know why Destroy is never called? What's the point in having it if it's not running?<br><br>I'd be interested in hearing other solutions folks have implemented.<br><br>Cheers,<br><br>Liz Godwin
<br>