Engineering Dashboard - Source code - Missing source code - No violation bookmarks or details are available on this violation object source code will be displayed instead when applicable

Created by Amine Benarbia, last modified by John McMahon on Sep 20, 2022
Purpose

This page will help you when you get the following message instead of the source code: No violation bookmarks or details are available on this violation object source code will be displayed instead when applicable

For more information, refer to:

Applicable in CAST Version


Release

Yes/No

8.3.x (tick)
Applicable RDBMS

RDBM

Yes/No

CSS (tick)
Step by Step Scenario
  1. Take snapshot
  2. Open ED
  3. View the source code of an object
Action Plan
  1. Access "Simple REST Client" by entering the following link in browser
    http://<server>: <port>/CAST-AED/static/default.html,
    Where
    <server>: <port> is the server from where the Deployment folder is deployed,
    CAST-AED is the name of the deployed deployment folder

  2. Using the URI , retrieve the source code by running the following query - SQL Queries - CAST Central Base - Queries on source code - How to get the Rest API URL that retrieve the source code of an object

  3. Submit the generated URI:

    1. If the response status returns an error message then, this is an Issue of REST API, refer to the following page - REST API Component
    2. Else if the response status returns "OK"

      1. If the response does not return the source code, then run the following query to check if the source code is stored under the central schema - SQL Queries - CAST Central Base - Queries on source code - How to get source code of an object

        1. If the query returns the source code then this is an Issue of REST API, refer to the following page - REST API Component

        2. Else if the query does not return the source code, then run the following query to check if the source code is stored under the local schema - SQL Queries - CAST Knowledge Base - Queries on source code - How to get the source code of an object

        3. If the query returns the source code, then the issue maybe occurring during the source code uploading, as a temporary fix you can try to upload manually the source code via the standalone GUI based or CLI based tools - ED - Using the GUI and CLI tools. then contact CAST Technical Support to investigate the root cause of the issue.

          An example of root cause, is when the capture date of the snapshot was updated. This bug was fixed starting from CAST AIP 8.3.6

        4. Else if the query does not return the source code, then this is an analyzer issue, refer to the following page CMS Snapshot Analysis - Run Analyzer

      2. Else If the response returns the source code

        Then the issue is related to ED WAR ,contact CAST Technical Support and provide the following Relevant input

  4. Try increasing the tomcat memory by launching the exe file - \bin\ tomcatw.exe. You can refer memory for the steps to be followed. Once done, restart the tomcat service and access the dashboard.
  5. If the above steps do not resolve your issue, then contact CAST Technical Support with the following Relevant input 


Known Issues
  • When the size of the source file has exceeded the limit of 40000000 characters, source code might not be visible for some rules . If this is the issue then in  CAST-MS log you can see the message 'size exceeded to upload the source' for that particular file. This page  Engineering Dashboard - Source code - Missing source code - Size of the source file has exceeded the limit  explains what needs to be done if source code file size has exceeded the limit.
  • If the source code is not visible for power builder objects then please note that this feature is implemented starting from 8.3.13 AIP version. Before that it was a limitation to have no source code visible for power builder objects.
  • If the source code is not visible for particular quality rule called 'Avoid direct or indirect remote calls inside a loop' then try taking a new snapshot skipping analysis. This is a known scenario affecting this particular quality rule when latest snapshot is deleted and consolidated. In this case to synchronize the metric computation between KB&CB we need to take a new snapshot skipping analysis. If new snapshot is not resolving your issue then please apply the attached 2 procedures DSSAPP_SOURCE_POS_UPDATE & DIA_JEEPATH_GENERATE  on KB and take snapshot skipping analysis. 
  • If the source code is not available for the rule- 'Avoid cyclical calls and inheritances between namespaces content' then this is a normal behavior. This particular rule is not designed to provide any bookmark.
    Also, this rule is focusing on packages/namespace objects, so objects being violated are packages/namespace type and we don't have any source code stored for them normally.
    So the current behavior of the rule is just to show you the violated namespace object. 


Notes/comments

Related Pages