Skip to content

Conversation

@he-is-harry
Copy link
Contributor

Fixed the issue in #233 where streaming blobs out of the database into another table can cause a deadlock

  • Added a "blocked" mode to the Queue which prevents tasks from running except for the blocking task and READ_LOB tasks
  • Modified ExecuteTask's run to free the queue while it waits for the Writer's getParameters
    • The callback of getParameters will enqueue the task again to send the packet
    • Before the freeing of the queue to the next task, ExecuteTask will block the queue to only allow itself and READ_LOB tasks to run
      • This prevents issues where exec's can run at the same time which will lead to HANA disconnecting and sending invalid LOB locator id errors

Fixed the issue in SAP#233 where streaming blobs out of the
database into another table can cause a deadlock
- Added a "blocked" mode to the Queue which prevents tasks from running
except for the blocking task and READ_LOB tasks
- Modified ExecuteTask's run to free the queue while it waits for the
Writer's getParameters
    - The callback of getParameters will enqueue the task again to send
the packet
    - Before the freeing of the queue to the next task, ExecuteTask will
block the queue to only allow itself and READ_LOB tasks to run
        - This prevents issues where exec's can run at the same time
which will lead to HANA disconnecting and sending invalid LOB locator id
errors
@BobdenOs
Copy link
Contributor

Please also refer to bugzilla 323457 and jira 23394. When that underlying issue is resolved it allows the client to remove the queue completely. Which provides additional benefits, but requires the client to consider the packet count in the responses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants