Can you provide the workspace and logging. Can you test if it also crashes when you only read data with the smallworld reader? Are you running 64 or 32 bits?
Can you provide the workspace and logging. Can you test if it also crashes when you only read data with the smallworld reader? Are you running 64 or 32 bits?
I've also done test sollely with readers and it also crashes. We're running on 32 bit. Workspace and log is also attached.
export-sw-gml.fmw
fmejob-114822log.txt
I've also done test sollely with readers and it also crashes. We're running on 32 bit. Workspace and log is also attached.
export-sw-gml.fmw
fmejob-114822log.txtDid you follow the instructions from this link?
https://knowledge.safe.com/articles/107/fme-and-smallworld-configuration-options.html
yup, we've been doing it for years and many other workspaces. And this is first time this kind of error occured.
1. Have you tested the workspace using desktop on the same server/machine where the server is installed?
2. Is your desktop and server versions the same?
1. Have you tested the workspace using desktop on the same server/machine where the server is installed?
2. Is your desktop and server versions the same?
Yes and yes :)
We've detected that problem might be in one feature type (gis.building_location_regular). If I use this workspace reading everything but that feature type... All ok. If I run it only with building_location_regular... Also ok. If I run it together... crash
1. Have you tested the workspace using desktop on the same server/machine where the server is installed?
2. Is your desktop and server versions the same?
For the immediate why don't you create 2 workspaces and use a fmeServerjobsubmitter transformer in a 3rd worksoace to run them consecutively . not sure if you can do with this temporary solution
For the immediate why don't you create 2 workspaces and use a fmeServerjobsubmitter transformer in a 3rd worksoace to run them consecutively . not sure if you can do with this temporary solution
yes, thank you. we've been working on few workarounds also inside code and FME. I'd really like to find out why is this happening...
yup, we've been doing it for years and many other workspaces. And this is first time this kind of error occured.
Can you log any feature that's coming out of the reader before it crashes?
Use a GeometryValidator to check and fix.
Hi
@zzupljanin - FYI.. FME Server will resubmit jobs that fail due to FME Engine crashes for a maximum of 3 times. This parameter is set by default and can be modified in a configuration file. Any changes will require a restart of FME Server.
<FMEServer_InstallDir>/Server/fmeServerConfig.txt
(~Line 422) MAX_FAILED_TRANSACTION_REQUEST_RETRIES=3
"Maximum number of times a failed transaction request will be automatically resubmitted for processing, after which the failed request is cancelled. A value of < 0 means that no maximum limit is imposed, and failed transaction requests will be automatically resubmitted indefinitely. A value of 0 means that automatic resubmission is disabled."
I've also done test sollely with readers and it also crashes. We're running on 32 bit. Workspace and log is also attached.
export-sw-gml.fmw
fmejob-114822log.txt@zzupljanin - Re: "t...] and after a few time Smallworld console returns stream exhausted tracebackc...]"
Can you include a snippet of the traceback from the Smallworld Console?
