Newbies Charles Phan Posted December 11, 2020 Newbies Posted December 11, 2020 Hi everybody, I have a problem with the FMSE 17 and Window Server 16, it stops working unexpectedly sometimes. My customer said: The problem appears when users access module A while another user runs the function to update the records on module B. (module A and B using the same source table). However, I can't reproduce this problem base on the above steps. Does any know what the problem is, please help me? Thanks
Wim Decorte Posted December 11, 2020 Posted December 11, 2020 First look for confirmation of how many times it happens, in the FMS event log. Look around that log and the Access log for any other indications, are they using PSoS? Any server-side script schedules running at times of the crashes? Also use the top call stats log to give you more info on activity at the time of the crashes. Often, FMSE crashes are caused by plugins, used server-side. Any plugins in use?
Newbies Charles Phan Posted December 12, 2020 Author Newbies Posted December 12, 2020 Thank, Wim I'm using the BaseElement plugin. Can you tell me which cases can make the FMSE crashes by the plugin?
Wim Decorte Posted December 12, 2020 Posted December 12, 2020 Plugins will make FMSE crash if they invoke functions that are not 'thread-safe', and there is more than one execution at the time. Meaning that one execution tramples all over the space of the other execution. (Overly simplifying the terminology here) BE has excellent documentation on their plugin functions and I believe they indicate which ones are not thread-safe. So make sure to update to the latest version and then check to see if the functions you are after are safe. If not, you'll have to find another way of doing what you are doing.
Newbies Charles Phan Posted December 14, 2020 Author Newbies Posted December 14, 2020 On 12/12/2020 at 6:33 PM, Wim Decorte said: Plugins will make FMSE crash if they invoke functions that are not 'thread-safe', and there is more than one execution at the time. Meaning that one execution tramples all over the space of the other execution. (Overly simplifying the terminology here) BE has excellent documentation on their plugin functions and I believe they indicate which ones are not thread-safe. So make sure to update to the latest version and then check to see if the functions you are after are safe. If not, you'll have to find another way of doing what you are doing. Thanks
Recommended Posts
This topic is 1508 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now