Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

  • 1.  TM1 REST API - 500 Internal Server Error on updating Edges

    Posted Tue January 14, 2020 05:20 PM

    Hello IBM,

    we noticed that sometimes our custom application that was updating Edges of a Hierarchy would fail with

    500 Internal Server Error 

    It happened when we did a POST request against the Edges property of a Hierarchy (to add more edges to it):

    POST Dimensions('something')/DefaultHierarchy/Edges

    I was now able to find a reproduceable case.

    It happens only when we do this update request at the same time, while the TM1 server is busy serving an MDX request against a cube that contains the dimension (that is being updated).

    We are running TM1 Server version 11.4.00007.5

    Is the dev team aware of this issue? Is it perhaps already addressed in a more recent version of the TM1 Server?
     

    Cheers,

     

    Marius



    ------------------------------
    Marius Wirtz
    ------------------------------

    #PlanningAnalyticswithWatson


  • 2.  RE: TM1 REST API - 500 Internal Server Error on updating Edges

    Posted Wed January 15, 2020 07:06 AM
    Hi Marius,

    I don't recognize this as a known issue.  However, it would help if you can confirm the problem can be reproduced on a current version of TM1 Server (e.g Planning Analytics 2.0.9).

    I wonder if the problem is specific to lock contention.  Take a look at the following Technote: https://www.ibm.com/support/pages/write-tm1-server-debug-logging-alternate-file.  This provides an example of how to enable debug logging for both lock contention and REST API.  You could try enabling both of these logging options until the problem reoccurs, and review the logging to determine if lock contention happened at the same time as the HTTP 500 response from TM1.  In the example in that Technote the lock exception debug logging is written to a lock.log file and the REST API request/response logging is written to a restapi.log file (both in the same directory as tm1server.log).

    The rest api logging will also help confirm the issue is not with the JSON body of the request to update the Edge.





    ------------------------------
    Stuart King
    IBM Planning Analytics Offering Manager
    ------------------------------

    Original Message


  • 3.  RE: TM1 REST API - 500 Internal Server Error on updating Edges

    Posted Fri April 03, 2020 05:53 AM
    Hi Stuart,

    sorry for the late response on this one.
    I can confirm that the issue does not occur on the TM1 Server version 11.7.00000.4

    We can close this issue.

    ------------------------------
    Marius Wirtz
    ------------------------------

    Original Message


Related Content