Skip to main content
  • EN

Folks,

As I become more familiar with FME my questions are getting a little more esoteric.

I have one workspace that I've been developing for sometime. Weeks for the purposes of scale.

I rarely close my sessions or even shutdown my PC. That's a general rule rather than anything specific to FME.

One AttributeManager with a conditional rule that was changing field values from upper case to proper case just stopped working. A later process that was using this proper case value consequently stopped working. Bear in mind the processing continued just getting the unmodified values.

I wrapped one of the values being matched with quotes eg If owner = "XCON", and ran the workspace. This didn't work but other conditions in the same field did work. I switched it back to the original syntax If owner = XCON and ran it again and it all just started working again.

I've used apps where a periodic restart\\reopen seems to flush any lingering threads and all seems to run cleanly again.

Am I experiencing some transient flakiness or is it some other known issue?

I don't know about FME, but even Windows can get "flaky" if you leave it running for weeks. I always make at least one reboot per week, as a preventative measure to prevent unexpected craches (and associated data loss). But maybe it's just because I grew up with Windows 3.1 and old habits die hard.

I don't know about FME, but even Windows can get "flaky" if you leave it running for weeks. I always make at least one reboot per week, as a preventative measure to prevent unexpected craches (and associated data loss). But maybe it's just because I grew up with Windows 3.1 and old habits die hard.

Thanks @david_r. Well, I beat you. I grew up on DOS. I realise nothing is infallible but modern OS's seem to be more tolerant of the need to be shutdown and restarted. This is also based on years of personal experience like your own. So does my scenario just sound like my FME workspace flaked out or is it some other issue that can affect an AttributeManger in the way I've described I'm not aware of?

 

Thanks @david_r. Well, I beat you. I grew up on DOS. I realise nothing is infallible but modern OS's seem to be more tolerant of the need to be shutdown and restarted. This is also based on years of personal experience like your own. So does my scenario just sound like my FME workspace flaked out or is it some other issue that can affect an AttributeManger in the way I've described I'm not aware of?

 

At least DOS was very stable so long as the programs behaved. Then came Windows...

 

Bought my first PC in 1988, not sure if I win a prize 😉
Thanks @david_r. Well, I beat you. I grew up on DOS. I realise nothing is infallible but modern OS's seem to be more tolerant of the need to be shutdown and restarted. This is also based on years of personal experience like your own. So does my scenario just sound like my FME workspace flaked out or is it some other issue that can affect an AttributeManger in the way I've described I'm not aware of?

 

Regarding the AttributeManager: such "flaky" behavior is almost always really difficult to pinpoint and reproduce, so for me it's impossible to tell if it's related. Never heard of anything like it, at least.
Regarding the AttributeManager: such "flaky" behavior is almost always really difficult to pinpoint and reproduce, so for me it's impossible to tell if it's related. Never heard of anything like it, at least.
Thanks again @david_r. That's the sort of info I'm after. When you're new at an application you doubt yourself initially. Later you doubt the system when something goes wrong. I'm just trying to get a feel for what might be possible and whether to look in the mirror or look at the screen. ;)

 

Thanks again @david_r. That's the sort of info I'm after. When you're new at an application you doubt yourself initially. Later you doubt the system when something goes wrong. I'm just trying to get a feel for what might be possible and whether to look in the mirror or look at the screen. ;)

 

From my own personal experience, most problems originate about 50cm in front of the monitor 😉
Thanks again @david_r. That's the sort of info I'm after. When you're new at an application you doubt yourself initially. Later you doubt the system when something goes wrong. I'm just trying to get a feel for what might be possible and whether to look in the mirror or look at the screen. ;)

 

or grabing the wrong pair of glasses in the morning....

 

 

Reply


Community Stats

30,133
Posts
114,389
Replies
37,772
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.