[
https://issues.jboss.org/browse/TEIID-2676?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2676:
---------------------------------------
To elaborate more on an analogy I'm alluding to is that a non-strict DNA is the moral
equivalent of a java timed wait. If you do
{code}
synchroized(foo) {
foo.wait(1000);
}
{code}
you may wait 1000 ms, but there isn't a hard guarantee either way - you may be
spuriously woken up early and you may due to other factors won't necessarily resume
after exactly 1000 ms.
So with the wait and the non-strict DNA it would be considered a best practice (or in the
DNA case basically required given the number of wake-ups that can occur) to use some logic
to ensure that the wait exit condition has been met:
{code}
synchronized(foo) {
while (!done) {
foo.wait(timeRemaining);
}
}
{code}
So if you don't strictly want to wait, then you should probably have translator logic
that knows a little more about when it can/should resume.
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