Issue #711 has been updated by Raphaël Ouazana. Status changed from Assigned to Feedback % Done changed from 0 to 100
Fixed. Note that if your task are independent you should launch different LSC process. But as this break back-compatibility, fixed anyway. ---------------------------------------- Bug #711: JavaScript error while executing a task causes subsequent tasks not to execute. http://tools.lsc-project.org/issues/711 Author: Jon Kidder Status: Feedback Priority: Normal Assigned to: Raphaël Ouazana Category: Core Target version: 2.1.1 Problem in version: 2.1.0 I have upgraded my development environment from LSC 2.0.3 to LSC 2.1 and I've noticed a change in error handling that is undesirable in my implementation. In 2.1, one of my tasks encounters a JavaScript error, and then subsequent tasks in the same lsc.xml file don't execute. I'm running the same lsc.xml in my production environment on 2.0.3. It is generating the same errors in the same task, but, subsequent tasks continue to execute. I have 4 tasks defined in my lsc.xml file. They are named: <pre> <task> <name>LSC_Employees_V2</name> <task> <name>LSC_Core_Automatons_V2</name> <task> <name>LSC_Core_Groups_V2</name> <task> <name>LSC_Employee_PWD_V2</name> </pre> Here's an excerpt of what I see in the logs for my 2.1 run in development: <pre> Jul 10 08:10:05 - INFO - Starting sync for LSC_Core_Automatons_V2 Jul 10 08:10:49 - INFO - All entries: 3009, to modify entries: 0, successfully modified entries: 0, errors: 0 Jul 10 08:10:49 - INFO - Starting sync for LSC_Core_Groups_V2 Jul 10 08:10:54 - ERROR - Error while reading entry CN=Enterprise Admins,CN=Users,DC=ds,DC=aepsc,DC=com: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: 'DC=corp,DC=aepsc,DC=com' ]; remaining name 'CN=Enterprise Admins,CN=Users,DC=ds,DC=aepsc,DC=com' Jul 10 08:10:54 - ERROR - Fail to compute expression: Reason: javax.script.ScriptException: sun.org.mozilla.javascript.internal.WrappedException: Wrapped java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 (<Unknown source>#139) in <Unknown source> at line number 139 Jul 10 08:10:54 - ERROR - Error while synchronizing ID {samaccountname=Administrators}: org.lsc.exception.LscServiceException: javax.script.ScriptException: sun.org.mozilla.javascript.internal.WrappedException: Wrapped java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 (<Unknown source>#139) in <Unknown source> at line number 139 Jul 10 08:19:39 - ERROR - All entries: 33776, to modify entries: 18, successfully modified entries: 18, errors: 2 Jul 10 08:19:39 - ERROR - Error while closing service. Jul 10 08:19:39 - ERROR - Error while closing service. Jul 10 08:19:39 - ERROR - Error while closing service. Jul 10 08:19:39 - ERROR - Error while closing service. Jul 10 08:19:39 - ERROR - Error while closing service. Jul 10 08:19:39 - ERROR - Error while closing service. </pre> The task that generates the error continues to run to completion but then there are no log entries indicating that the other 2 tasks were ever started. Here's an excerpt of my log when I comment out the offending task: <pre> Jul 10 09:04:22 - INFO - Starting sync for LSC_Core_Automatons_V2 Jul 10 09:05:10 - INFO - All entries: 3009, to modify entries: 0, successfully modified entries: 0, errors: 0 Jul 10 09:05:10 - INFO - Starting sync for LSC_Employee_PWD_V2 Jul 10 09:07:28 - INFO - All entries: 25378, to modify entries: 546, successfully modified entries: 546, errors: 0 Jul 10 09:07:28 - INFO - Starting sync for LSC_Employees_V2 Jul 10 09:11:03 - ERROR - All entries: 25381, to modify entries: 2494, successfully modified entries: 2493, errors: 1 Jul 10 09:11:03 - ERROR - Error while closing service. Jul 10 09:11:03 - ERROR - Error while closing service. Jul 10 09:11:03 - ERROR - Error while closing service. Jul 10 09:11:03 - ERROR - Error while closing service. </pre> All 3 tasks ran to completion and you can see from the counts that the last two tasks haven't run in quite a while. You'll also notice the count of "closing" errors is different?? Here's an excerpt from my production log running the same lsc.xml under 2.0.3 <pre> Jul 10 09:00:08 - INFO - Starting sync for LSC_Core_Automatons_V2 Jul 10 09:00:49 - ERROR - All entries: 3009, to modify entries: 0, successfully modified entries: 0, errors: 1 Jul 10 09:00:49 - INFO - Starting sync for LSC_Core_Groups_V2 Jul 10 09:00:54 - ERROR - Error while reading entry CN=Enterprise Admins,CN=Users,DC=ds,DC=aepsc,DC=com: javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: 'DC=corp,DC=aepsc,DC=com' ]; remaining name 'CN=Enterprise Admins,CN=Users,DC=ds,DC=aepsc,DC=com' Jul 10 09:00:54 - ERROR - javax.script.ScriptException: sun.org.mozilla.javascript.internal.WrappedException: Wrapped java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 (<Unknown source>#139) in <Unknown source> at line number 139 Jul 10 09:11:29 - ERROR - All entries: 33775, to modify entries: 12, successfully modified entries: 9, errors: 3 Jul 10 09:11:29 - INFO - Starting sync for LSC_Employees_V2 Jul 10 09:15:15 - INFO - All entries: 25381, to modify entries: 1, successfully modified entries: 1, errors: 0 Jul 10 09:15:15 - INFO - Starting sync for LSC_Employee_PWD_V2 Jul 10 09:18:23 - INFO - All entries: 25378, to modify entries: 25, successfully modified entries: 25, errors: 0 </pre> The same JavaScript error occurs in production but all of the tasks execute and run to completion. I will attempt to build a much simpler sample configuration that also demonstrates this behavior. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
