Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1732

The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store protocol violation errors

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
    • 10.2.2.0, 10.3.1.4
    • SQL, Store
    • None

    Description

      Don't have the exact details, but remember noticing it a while ago. I think the store transaction context closes the transaction on such an error, while the language conneciton context just rollsback the transaction or the statement. I think the best and consistent approach would be to close the connection.

      Attachments

        1. derby1732.diff.txt
          3 kB
          Sunitha Kambhampati
        2. derby1732.stat.txt
          0.2 kB
          Sunitha Kambhampati

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            skambha Sunitha Kambhampati
            djd Daniel John Debrunner
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment