In my SW to Postgres geodatabase dynamic translation using SchemaMapper, there are two attempts to connect to Smallworld and the second one always hangs so the translation doesn't complete. Anyone know a way around this?
Best answer by erik_jan
Sorry, but I found this line twice in the log:
Connecting to Smallworld on localhost:30000 using service FME
I can not understand why FME would try to connect twice to SmallWorld if only one Reader is involved (and not SmallWorld writer of connecting transformers).
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
We're on Smallworld Version 4.2 and FME version 2017.1 Build 17539 - WIN32
+22- Contributor
- 2179 replies
From the log file it seems you are using two readers to the same Smallworld instance using the same port. SmallWorld can limit the number of connections. Not sure what Magik command to use to set the number of allowed connections higher.
Could you use one reader and import both tables in that one reader instead? Then you will need only one connection to SmallWorld to read both tables.
Look to import using the Readers > Import Feature Types menu.
From the log file it seems you are using two readers to the same Smallworld instance using the same port. SmallWorld can limit the number of connections. Not sure what Magik command to use to set the number of allowed connections higher.
Could you use one reader and import both tables in that one reader instead? Then you will need only one connection to SmallWorld to read both tables.
Look to import using the Readers > Import Feature Types menu.
+14- Safer
- 671 replies
I tested in FME 2017.1 Build 17539 with 1 Smallworld 4/5 Reader and multiple Feature Types, but I could not reproduce this issue.
Though I must note that I am connecting to Smallworld 4.3.0.7 (and likely using newer DLLs). We unfortunately do not have a Smallworld 4.2 installation to test with.
I tested in FME 2017.1 Build 17539 with 1 Smallworld 4/5 Reader and multiple Feature Types, but I could not reproduce this issue.
Though I must note that I am connecting to Smallworld 4.3.0.7 (and likely using newer DLLs). We unfortunately do not have a Smallworld 4.2 installation to test with.
Yes I tried creating a new workspace and got the same result unfortunately. We're moving our enterprise GIS from Smallworld to ESRI on postgres SDE (and were hoping to leverage FME in translating directly to PG geodb). So we won't be upgrading to the SW version you have.
+22- Contributor
- 2179 replies
- Best Answer
Sorry, but I found this line twice in the log:
Connecting to Smallworld on localhost:30000 using service FME
I can not understand why FME would try to connect twice to SmallWorld if only one Reader is involved (and not SmallWorld writer of connecting transformers).
+22- Contributor
- 2179 replies
Yes I tried creating a new workspace and got the same result unfortunately. We're moving our enterprise GIS from Smallworld to ESRI on postgres SDE (and were hoping to leverage FME in translating directly to PG geodb). So we won't be upgrading to the SW version you have.
Spatialbiz plugin for FME
Sorry, but I found this line twice in the log:
Connecting to Smallworld on localhost:30000 using service FME
I can not understand why FME would try to connect twice to SmallWorld if only one Reader is involved (and not SmallWorld writer of connecting transformers).
+22- Contributor
- 2179 replies