[
https://issues.jboss.org/browse/TEIID-2676?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-2676:
--------------------------------------
Thanks for detailed explanation.. I understand. When multiple executions throw DNA with
strict=true, the engine effectively switches from the Request.ANY strategy to the
Request.ALL strategy.
I see now that the semantics of the timeout don't quite line up with the semantics
that I want, which is no big deal since I can make the appropriate change in the
delegating translator. I'll close out this jira and report my findings on the forum
thread.
Delay in DataNotAvailableException not honored when isForkable=false
--------------------------------------------------------------------
Key: TEIID-2676
URL:
https://issues.jboss.org/browse/TEIID-2676
Project: Teiid
Issue Type: Bug
Reporter: Mark Addleman
Assignee: Steven Hawkins
Attachments: DelayNotHonored.java
It appears that when isForkable=false, the delay specified in DataNotFoundException is
not honored. I have seen similar behavior even when isForkable=true but it's a
Heisenbug: when I add logging, it goes away. It smells like a race condition.
--
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