Use Sessions (AS)

5 posts, 1 answered
  1. Markus Grigoleit
    Markus Grigoleit avatar
    30 posts
    Registered:
    04 Jun 2019
    Answered
    06 Jan
    Link to this post
    We have a bug that appears to exist after we call a BE.
    It says that i cannot empty a temp-table when Tracking-changes is set to true on its handle.

    The problem is, that this does not happen after each call. So i wanted to debug this with a message, but since the Session is randomly picked its hard to get the message out of the right Session.

    Is there a way i could print this messages for every Session (from within the BE)?
    I tried to limit the sessions to 1 but its not working,
  2. Peter Judge
    Peter Judge avatar
    3 posts
    Registered:
    11 Aug 2022
    06 Jan in reply to Markus Grigoleit
    Link to this post
    Hi Markus,


    Is there a way i could print this messages for every Session (from within the BE)?


    The short answer is no. An ABL (agent) session does not have any knowledge of any other sessions in its agent. Only the agent and the session manager know this, and there is no way to tell either one of them to run something in all sessions.

    You can idenfity the ABL session used to service a request, using the request ID. This value looks something like "ROOT:a:0000063f" .It is written automatically into PASOE agent log. You can get this value from the access log. This log tells you which HTTP requests were made, and what their request ID is.

    This is not always very useful for ABL clients (ie APSV requests) - it can be hard to see what was actually run from that information.

    In this case, you can use the Telemetry Service. This reports more specific information about a request:  what was the BE called (the service name) and the method called (the service request). It also contains the agent and ABL session IDs, which are also useful. With this information you can more easily see all of the requests made to a particular ABL session, and so potentially figure out more easily what is causing the issue.

    -- peter
  3. Mike Fechner
    Mike Fechner avatar
    302 posts
    Registered:
    14 Sep 2016
    06 Jan in reply to Markus Grigoleit
    Link to this post
    Do you have the stack trace of the error message?
  4. Markus Grigoleit
    Markus Grigoleit avatar
    30 posts
    Registered:
    04 Jun 2019
    06 Jan in reply to Mike Fechner
    Link to this post
    Until now i couldnt reproduce it properly so i only got one screenshot that says:

    message: "Sie dürfen die temp-Tabelle eatrk nicht LEEREN, wenn TRACKING-CHANGES wahr ist. (12758)"

    This error wasnt shown in our agent.log file. It was just the payload of the HTTP-response.


  5. Peter Judge
    Peter Judge avatar
    3 posts
    Registered:
    11 Aug 2022
    06 Jan in reply to Markus Grigoleit
    Link to this post

    The callstack of the error can be written into the HTTP response, if it isn't already. The value of the JsonErrorWriteCallStack property in .restapplicationsettings must be TRUE, and the -errorstack parameter set (or SESSION:ERROR-STACK-TRACE = TRUE).

    The JSON payload with the error should then have a callStack property.
5 posts, 1 answered