Hi Henrik,
try turning off the parallel processing: if the error disappears it could be an indication of a problem there. If not, it might be your data.
For what it's worth, my experiences with the parallel processing option in FME have been quite varied in outcome, both in terms of stability and performance. Some scenarios seem to be less suited for this option than others, without me having found a good explanation for how and why.
Even when the results are correct, I would alway recommend making several timed runs with and without this option to see how it influences the performance. There can be quite a lot of overhead for this option depending on how you use it, so it's not always a guarantee for improved performance.
David
Thanks David,
Yes probably the best solution to turn of the parallel processing.
Pity though, since it reduce the job with 6 hours (when it works)
Yes, that's a pity. You could, however, also consider using the WorkspaceRunner to replicate the parallel processing behavior, if possible. I have good experiences with this type of solution.
For curiosity, are you using FME2013sp1? If not, it would be interesting to hear if that makes a difference.
Lykke til.
David
Hi Henrik
My first thought was bad geometry - which kills the child process. But if it runs OK without parallel processing then this probably isn't the case.
Either way, if you could
submit this to our support team we'll be happy to investigate and try to get the problem fixed. Please include your workspace and data if possible, and details of the operating system, so we can try and replicate your setup as closely as possible.
Regards
Mark
Mark Ireland
Product Evangelist
Safe Software.