Uploaded image for project: 'External API Framework'
  1. External API Framework
  2. EXTAPI-221

ExtAPI is filling the logs at info level while polling SO for orderItem status

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Medium Medium
    • Dublin Release
    • None
    • NBI

      2019-03-19 15:12:59.721  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:12:59.740  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:12:59.757  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:03.145  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:03.170  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:03.188  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:05.216  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:05.238  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:05.261  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:07.287  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:07.304  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:07.321  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:09.345  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:09.362  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:09.379  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

      2019-03-19 15:13:11.409  INFO 1 — [   scheduling-1] org.onap.nbi.apis.serviceorder.SoClient  : response status : 200

       

      caused by

       

      private void logResponseGet(String url, ResponseEntity<GetRequestStatusResponse> response) {

              if (response != null) {

                  if (LOGGER.isDebugEnabled()) {

                      LOGGER.debug("response body : {}", response.getBody().toString());

                  }

                  LOGGER.info("response status : {}", response.getStatusCodeValue());

                  if (LOGGER.isWarnEnabled() && !response.getStatusCode().equals(HttpStatus.OK)) {

                      LOGGER.warn("HTTP call SO on {} returns {} , {}", url, response.getStatusCodeValue(),

                          response.getBody().toString());

                  }

              } else {

                  LOGGER.info("no response calling url {}", url);

              }

          }

       

          private void logE2EResponseGet(String url, ResponseEntity<GetE2ERequestStatusResponse> response) {

              if (response != null) {

                  if (LOGGER.isDebugEnabled()) {

                      LOGGER.debug("response body : {}", response.getBody().toString());

                  }

                  LOGGER.info("response status : {}", response.getStatusCodeValue());

                  if (LOGGER.isWarnEnabled() && !response.getStatusCode().equals(HttpStatus.OK)) {

                      LOGGER.warn("HTTP call SO on {} returns {} , {}", url, response.getStatusCodeValue(),

                          response.getBody().toString());

                  }

              } else {

                  LOGGER.info("no response calling url {}", url);

              }

         

            aosull01 aosull01
            aosull01 aosull01
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: