Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-290

Internal Server Error when creating the same data node twice

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Medium
    • Resolution: Done
    • Honolulu Release
    • Honolulu Release
    • CPS-Core-REST
    • None

    Description

      Scenario:

      Create the same data node twice with POST "protocol://host:port/cps/api/v1/dataspaces/dataspace-name/anchors/anchor-name/nodes" endpoint

      Actual Behaviour:

      An Internal Server Error occurs

      {
    "status": "500 INTERNAL_SERVER_ERROR",
    "message": "could not execute statement; SQL [n/a]; constraint [uq_fragment_xpath]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement",
    "details": "Check logs for details."
}

      See attached log file

      Expected behaviour:

      Http Error code 4xx with an explanation message.

       

       

      Attachments

        1. error.log
          13 kB
        2. log.txt
          38 kB

        Issue Links

          blocks

          Task - A task that needs to be done. CPS-319 Create Docker Image with all bugfixes for Honolulu Release

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed
          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. CPS-306 Internal Server Error when creating the same data node twice

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              niamhcore Niamh Core
              brusak Bruno Sakoto
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: