[teiid-issues] [JBoss JIRA] (TEIID-2410) issues with output buffer blocking

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-2410:
----------------------------------

              Summary: issues with output buffer blocking  (was: add tuning for lots of active plans)
           Issue Type: Bug  (was: Quality Risk)
        Fix Version/s: 8.3
    Affects Version/s: 7.7
          Description: 
when a local connection (regardless of using the calling thread) blocks on the output buffer (which cannot happen with forward only and using the calling thread, but due to another issue can occur with a scroll insensitive result) no corresponding process thread is awakened to process pending work.

Output blocking should also be disabled for non-forward only results.  This was disabled at some point by a refactoring to reuse the output buffer from the plan.

  was:When an active plan is not processing it will still be holding memory against the buffer manager reserve count.


    
> issues with output buffer blocking
> ----------------------------------
>
>                 Key: TEIID-2410
>                 URL: https://issues.jboss.org/browse/TEIID-2410
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.7
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.3
>
>
> when a local connection (regardless of using the calling thread) blocks on the output buffer (which cannot happen with forward only and using the calling thread, but due to another issue can occur with a scroll insensitive result) no corresponding process thread is awakened to process pending work.
> Output blocking should also be disabled for non-forward only results.  This was disabled at some point by a refactoring to reuse the output buffer from the plan.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira