• YO
    August 5, 2015 at 8:54 pm #598


    The datepicker doesn’t look functioning correctly. When I click a date in the control, system hangs saying “due to long running script, devkor002 does not respond”.

    I tried explorer and fire fox to test but the results are the same.

    Anybody having the same issue? or any idea to fix the issue?





    Internet explorer version 11

    BPM Server version 8.5.6

    SPARK version 8.5.6



    August 6, 2015 at 7:13 am #601


    Thanks for the post per our email exchange.

    August 12, 2015 at 12:16 pm #649

    Is there any body having the same issue (endless loops) when using datepicker control?

    Thanks in advance,

    August 17, 2015 at 8:37 am #659

    I just tested out the Datepicker control with Spark 4.0.4- in PD and I didn’t receive the same error within Firefox, Internet Explorer, or Chrome. Which version of Spark are you using?

    August 19, 2015 at 8:09 pm #684

    I am using the exactly same environment. Spark404-856 in PD856.

    When I upgrade to PD856, I have upgraded to Webspere 8.5.5 fix pack 5 and PD8.5.6

    After installing PD, I have run DBUpgrade.bat.

    Am I missing anything that may have caused my environment is causing the problem?

    Any comment will help. thanks

    August 21, 2015 at 2:33 pm #686

    Could you describe the problem/error you are experiencing or attach a screenshot?

    August 24, 2015 at 1:03 am #687

    To explain more detail about the issue,
    I have downloaded “SPARK -8.5.6 (CE-000 ) and ran DatePicker showcase.
    The symphtom in Firefox is that I see error in the firefox console, which says, “DatePicker._setDate() error: InternalError: too much recursion”.
    And the log shows me 24 times of the following message.
    bpmext_control_InitDatePicker/this.constructor.prototype._proto._setDate() BPMExt-Control-DatePicker.js:12
    bpmext_control_InitDatePicker/this.constructor.prototype.change() BPMExt-Control-DatePicker.js:40
    a.a.ec/f.set() bpmext.js:21
    bpmext_control_InitDatePicker/this.constructor.prototype.load/this.onChangeHandle<() BPMExt-Control-DatePicker.js:36
    .cache[“dojo/_base/lang”]/</lang.hitch/<() dojo.js:8
    _2db/</_2e1() dojo.js:8
    DatePicker.prototype._setDate() main.js:1638
    DatePicker.prototype.updateControl() main.js:938
    And then, the following error is shown.
    Call stack: bpmext_control_InitDatePicker/[email protected]://devkor002:9443/teamworks/webasset/2064.0680bb9d-b6d4-4713-b478-4daafc93f58d/W/BPMExt-Control-DatePicker.js:40:1
    a.a.ec/[email protected]://devkor002:9443/teamworks/webasset/2064.0680bb9d-b6d4-4713-b478-4daafc93f58d/W/BPMExt-Core.zip/com/salientprocess/bpm/views/bpmext.js:21:153
    _2db/</[email protected]://devkor002:9443/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:69445
    [email protected]://devkor002:9443/teamworks/webasset/2064.0680bb9d-b6d4-4713-b478-4daafc93f58d/W/BPMExt-Lib-DatePicker.zip/lib/main.js:1638:4
    [email protected]://devkor002:9443/t[…]
    and when I select a date in date picker, the displayed date is different from what I selected. in the attached picture, I have selected Aug 20, 2015, but the output text is 04/02/2015.
    When I used IE (Ver 11), it just hangs when I select a date. (It seems by default IE doesn’t stop endless loop automatically).

    January 25, 2016 at 6:45 pm #1310


    Does anybody know how to fix this problem?

    I have the same kind of issue now with SPARK4.2.1.

    InternalError: too much recursion
    [object Object] dojo.js:8:290005

    DatePicker._setDate() error: InternalError: too much recursion bpmext.js:821:4

    Call stack: .cache[“com.ibm.bpm.coach/Stateful”]/</<.enableSystemNotifications/this._systemCallbackHandle<@https://localhost:9449/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:48222
    .cache[“dojo/Stateful”]/</<.watch/this._watchCallbacks/[email protected]://localhost:9449/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:190515
    .cache[“dojo/Stateful”]/</<.watch/[email protected]://localhost:9449/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:190584
    [email protected]://localhost:9449/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:444153
    .cache[“dojo/Stateful”]/</<[email protected]://localhost:9449/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:190063
    [email protected]://localhost:9449/teamworks/script/coachNG/dojo/1.10.3/dojo/dojo.js:8:146122

    January 31, 2016 at 10:16 pm #1323

    Anybody can double check? It has been the reason I can’t use SPARK toolkit.

    I would really appreciate it if anybody can dig more into the issue.

    SPARK Support
    February 1, 2016 at 6:05 am #1324

    We are unable to reproduce this issue locally using 4.2.1 CE or EE.  What options are you using on the DTP?  Is the DTP nested inside any other controls?  What Browser are you using.





    February 1, 2016 at 6:20 am #1325

    Great Thanks for prompt reply.

    I just opened “date picker showcase” , ran without modifying anything and I have the problem.

    I am using IE11.0.27 /Firefox 37.0.2. All have the same problem. I foratted my computer and re-installed everything and  I even tried using my collegue’s computer. But the symptom is all same since version SPARK 4.0.4.

    I wonder my local UTC+9 Korea has anything to do with this issue.  My BPM server time zone is also UTC+9.



    February 1, 2016 at 10:48 pm #1326


    Thanks for your support.

    It seems something wrong with handling localized time.

    when I set timezone of my windows to CST it works fine.But when I set timezone to JST it doesn’t work.


    February 1, 2016 at 11:02 pm #1327

    Hi, Haseshin, Thanks for your information.

    I also found any timezone with UTC + has problem. e.g. UTC -6 , UTC-1, UTC 0 are OK. UTC +1, UTC+9(korea) are Not Ok.


    Hi, sparksupport team,

    This may mean any country in Europe and Asia can’t use SPARK toolkit.

    Please investigate timezone problem and hopefully get us fix soon.


    February 2, 2016 at 12:04 am #1328

    Hi YO-san

    I checked BPMExt-Control-DatePicker.js

    the code compare ‘viewDate’ and ‘date’ , but viewDate is always 1 day ahead and this block is called infinitely.

    if((view._instance.pickerControl.viewDate && view._instance.pickerControl.viewDate.getTime()) != (date && date.getTime())){

    So I fixed the code like this,

    if((view._instance.pickerControl.viewDate.getUTCDate()) != date.getUTCDate()+1){

    I’m not sure this is a right way to fix , but it works!

    (I also found when we put 2 ‘fixed’ datePicker with same binding on the same coach it doesn’t work….so it is not a right way to fix.)

    SPARK Support
    February 2, 2016 at 10:33 am #1330

    Our developer has tried to reproduce this issue, unsuccessfully.  Is there any chance you could send a small twx file that illustrates the problem


    February 2, 2016 at 4:50 pm #1331

    Dear sparksupport team,

    You don’t even need any sample. You can simply change your time zone above UTC+0 then, any datepicker control in the showcase will have the trouble.  Please take a look at the attachment.


    Brian French
    February 3, 2016 at 10:11 am #1334

    We have confirmed the issue are planning a hot fix.  We are tentatively looking at having this ready by Tuesday of next week.

    February 3, 2016 at 4:11 pm #1335

    Sounds great!

    I’m eagerly waiting for fix.

    SPARK Support
    February 8, 2016 at 3:28 pm #1365


    The fix has been applied to the Date Picker.

    You can download the SPARK Toolkit by logging into you account and going to your downloads here:


    Please let us know if you have any questions.


    SPARK Support

Viewing 20 posts - 1 through 20 (of 20 total)

You must be logged in to reply to this topic.

Start typing and press Enter to search