I have 2 server side scripts that occasionally overlap. When they do they crash the script engine.

Errors are below - but there are lots of these.

Aug 28, 2012 11:32:46 AM com.prosc.fmkit.Plugin setLastError

SEVERE: PluginFunction com.prosc.beanshell.CompiledFunction@f39b3a got an error with converted args [uPDATE BookDetails SET LowestUsedPrice=null, LowestUsedPriceCurrency='£', AmazonTotalUsed=4 ,AmazonSalesRank= WHERE zkAmazonASIN='0216889219', |]

com.prosc.fmkit.FmCalculationException: 8310

at com.prosc.fmkit.PluginContext.executeSql(PluginContext.java:180)

at com.prosc.beanshell.FMPro.executeSql(FMPro.java:148)

at com.prosc.beanshell.FMPro.executeSql(FMPro.java:142)

at com.prosc.beanshell.FMPro$executeSql.call(Unknown Source)

at scriptmaster.Module_MTYyNTQ1MjgzNgXX.run(scriptmaster.Module_MTYyNTQ1MjgzNgXX.script:1)

at com.prosc.beanshell.GroovyFunction.invoke(GroovyFunction.java:110)

at com.prosc.beanshell.CompiledFunction.invoke(CompiledFunction.java:78)

at com.prosc.fmkit.Plugin.invokeFunction(Plugin.java:333)

at com.prosc.fmkit.RegisterablePlugin.invokeFunction(RegisterablePlugin.java:77)

at com.prosc.fmkit.Plugin.invokeFunctionNoErrors(Plugin.java:314)

at com.prosc.fmkit.PluginBridge$3.run(PluginBridge.java:1055)

at com.prosc.fmkit.PluginBridge.runTask(PluginBridge.java:1264)

at com.prosc.fmkit.PluginBridge.doFunction(PluginBridge.java:1069)

Aug 28, 2012 11:32:46 AM com.prosc.beanshell.BeanShellPlugin setLastError

SEVERE: ScriptMaster bound variables: Parameters:

And

Aug 28, 2012 11:42:08 AM com.prosc.fmkit.PluginBridge pushContext

WARNING: pushContext called with function (com.prosc.beanshell.CompiledFunction@1542a75) when stack size is 1; this either means it was called re-entrantly, an idle handler was called without waiting for a return from a previous call, or pop was not called from last invocation. Current thread: Thread-27875

Each script runs perfectly on it's own. The ScriptMaster log file on the server shows everything in order and no errors.

Any help please??

Thanks

As you may know this looks like an issue with threading. The best workaround currently may be to set make sure the scheduled scripts do not overlap.

Thanks,

But I have found the same script running on it's own on the server can also exhibit the same behaviour.

It appears to only occur when the progressive backup is active as the script ran perfectly for 12 hours on a client machine, and on a different server when progressive backups were disabled