It's all about the answers!

Ask a question

why value set provider script can not work properly suddenly?


jane zhou (86331) | asked Jan 21 '20, 5:13 p.m.

 

Hi Someone who may concern,

       Our Value set provider can work properly long time, and we did not update the script, but suddenly, it start to report the error in server log as the following, and it can not work. ( Our RTC version is 6.0.6.1 IFix 009.)
 Error invoking value set provider '.....' in the project area with id '.....'. 
You can link to the project area definition using a URL similar to https://thehostname:9443/jazz/process/project-areas/...., where the host name, port and jazz context are configured for your installation. Contact your project area administrator for assistance.$
 java.lang.ArrayIndexOutOfBoundsException

     So, to simplify the condition, we disable all scripts to connect to any attribute, disable all conditions/default value/calculated Value with script, i.e. no script will be run, and only associate a string type attribute with a value set provider script provided by RTC as Fill in example.
      
      But result is still the same, RTC refuse to connect script with attribute with ArrayIndexOutOfBoundsException error, which is really confusing.   

/***********
* Licensed Materials - Property of IBM
* (c) Copyright IBM Corporation 2011. All Rights Reserved.
*
* Note to U.S. Government Users Restricted Rights: 
* Use, duplication or disclosure restricted by GSA ADP Schedule
* Contract with IBM Corp.
***********
/
dojo.provide("com.tst.release.ValueSetProvider");

(function() {
    dojo.declare("com.tst.release.ValueSetProvider", null, {

        getValueSet: function(attributeId, workItem, configuration) {
       
            var result= [];
            result.push("a");
            result.push("b");
            var myOldValue = workItem.getValue(attribute);
            return myOldValue;
           
        }
   });
})();

         We are wondering how we should resolve issue like this? 

         Thanks!

Best Regards,
Jane 

Accepted answer


permanent link
jane zhou (86331) | answered Jan 21 '20, 7:41 p.m.

 

After we restart the RTC server, the issue is resolved.
So it seems there are some internal issues in Server side caused the issue.

If you encountered the similar issue, you can try to restart server.

Ralph Schoon selected this answer as the correct answer

Your answer


Register or to post your answer.