[teiid-issues] [JBoss JIRA] (TEIID-2271) Timing issue when processing data from an XML stream

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-2271.
-----------------------------------

           Labels: 8.4CR2  (was: 8.2.CR1)
    Fix Version/s: 8.4
                       (was: 8.2)
       Resolution: Done


The 8.2 fix only addresses the happy path.  The updated 8.4 fix also conveys the exception to the tuplebuffer.  Decided at this point not to go with the workitem notification as to allow the fix to be easily back ported and to hopefully reduce the amount of the xquery result that needs to be written into the buffer (although any other blocking event will still cause the overall execution to block properly).
                
> Timing issue when processing data from an XML stream
> ----------------------------------------------------
>
>                 Key: TEIID-2271
>                 URL: https://issues.jboss.org/browse/TEIID-2271
>             Project: Teiid
>          Issue Type: Bug
>          Components: XML Connector
>    Affects Versions: 8.2
>            Reporter: Paul Richardson
>            Assignee: Steven Hawkins
>              Labels: 8.4CR2
>             Fix For: 8.4
>
>         Attachments: server.log
>
>
> Running a preview on an XML datasource causes a freezing of the gui. The main thread is stuck trying {{SocketInputStream.socketRead0}}, which never returns.
> The jboss log indicates a BlockedException has occurred and only when designer is forcibly terminated does the input stream read get cancelled.
> Discussions over the log indicate ...
> '... a timing issue where the asynch processing thread notifies after the processing thread has been detached and there's no other action that restarts the plan'
> Server log snippet attached.

--
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