Decision Management

Expand all | Collapse all

Error in Testing Scenario File

  • 1.  Error in Testing Scenario File

    Posted Sat November 28, 2020 11:39 PM

    Hi there, is there any sources I can refer to understand the error details produced when testing a scenario file of decision model services in decision center?
    I have been following step by step the tutorial on decision model services from the following link:

    Getting started with decision modeling (Step 5 Testing and Deploying):​
    When I want to test a scenario file, there are errors produced and result in my testing does not work.
    The error produced are:

    An error has occurred in preparing the test suite for execution. Contact your administrator.
    ilog.rules.teamserver.model.IlrTestingException: Error occurred while starting the job
    at ilog.rules.teamserver.ejb.service.validation.IlrTestSuiteService.asynchronousPrepare(
    at ilog.rules.teamserver.ejb.service.validation.PrepareArchiveThreadService$
    at java.util.concurrent.Executors$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$
    Caused by: Error occurred while starting the job
    at ilog.rules.teamserver.ejb.service.validation.IlrTestSuiteService.asynchronousPrepare(
    ... 6 more

    Need help to understand these errors and how to fixed it.

    Thank you.

    Azim MNasir

  • 2.  RE: Error in Testing Scenario File

    Posted Wed December 02, 2020 08:59 AM
    This looks like a configuration issue, unfortunately there is not enough information in this stack to diagnose the issue properly.
    Are you able to run testing for a Decision Service or do you see the same problem?    
    What server are you using how is it configured?

    Alain Robert

  • 3.  RE: Error in Testing Scenario File

    Posted Wed December 02, 2020 09:04 AM

     Azim, not that the link you provide is broken. I guess you're following this tutorial:

    The trace you show does not provide too much information, maybe you can search in the server logs (in case you're using the samples server it should be in your liberty profile <wlp-profile>/logs/messages.log) for a "Caused-by" exception following this one.

    Anyway the problem executing the scenario can be related to the format of the data in your excel file, double check that each data item has the correct format (number, text,...).


  • 4.  RE: Error in Testing Scenario File

    Posted Wed December 02, 2020 01:49 PM
    Hello Azim,

    the error you had means that the server defined in the test suite can not be reached in order to run the test suite.

    Either the server set in the test suite does not have a correct settings
    or the DecisionRunner  app is not working or not properly deployed

    Some explanation : in order to run "test and simulations",  Decision center forwards run requests to a web server where Decision Runner is deployed along with RES console web app.
    If using the sample Server, then DecisionCenter, DecisionRunner and the RES console are deployed on the same Liberty server.

    There error you had means that
    - DecisionRunner is not running
    - the configuration of a TestingAndSimulation server is not correctly set in Decision center.
    the TestSuite is not using the correct TestingAndSimulation server

    To conduct verification, you need to
    - log in  login as rtsAdmin in Decision Center
    - go to the Administration tab
    - go to the Servers section
    - in the server list ,  verify that you have a "Testing and simulation" usage server defined.
            If there is not such server, you need to create one, pointing to Decision Runner with the RES server login/password.
    - Over the server in the list with the mouse pointer, to show action buttons, then use the server testing button.
           If the result is OK, then you need to edit the test suite and make sure to explicitly select the validated "Testing and simulation" server .
           If the result is not OK, then edit the server and verify the DecisionRunner URL, and credentials used are correct, and that the DecsionRunner application is deployed correctly

    Please let us know if this helps.

    Best regards,
    Francois Gadrat