]
Paul Richardson resolved TEIIDDES-1474.
---------------------------------------
Resolution: Out of Date
Preview works successfully with these models. The 'HighNetWorthCustomers' and
'AccountHoldings' are dependent upon the stock quotes so the speed is dependent
upon the quotes' source (in my case a wsdl).
Preview Data on certain models causes JBDS to go into unrecoverable
loop
------------------------------------------------------------------------
Key: TEIIDDES-1474
URL:
https://issues.jboss.org/browse/TEIIDDES-1474
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview
Affects Versions: 7.1.1
Environment: Have attempted on both RHEL 6.3 and Mac OSX. Used JBDS 5.0 with
latest plugins and EDS 5.3.
Reporter: Blaine Mincey
Assignee: Paul Richardson
Fix For: 8.2.x-prod-eds6.0
When using the FinancialsDemo, our internal demo project
(
https://docspace.corp.redhat.com/docs/DOC-56653), previewing data from the
CustomerHoldings/BrokerageModel (models AccountHoldings, AccountValue, and
HighNetWorthCustomers) causes JBDS/Teiid to go into an unrecoverable loop where you must
abruptly "force quit" the IDE to regain control. I have also seen this behavior
when attempting to preview data from one of the included Web Services in the project.
The following snippet is repeated multiple times in the EDS server log at the time that
the process seems to get stuck in a loop:
2012-08-15 15:10:29,866 INFO [org.teiid.RUNTIME] (New I/O server worker #2-1)
org.teiid.query.tempdata.GlobalTableStoreImpl@644ec403 first member or timeout exceeded
2012-08-15 15:10:29,881 INFO [org.teiid.PROCESSOR] (New I/O server worker #2-1) Clearing
prepared plan cache for vdb
PREVIEW_70a7a0cb-5c46-4589-aa1c-9018517e0c0f_FinancialsDemo_project.1
2012-08-15 15:10:29,882 INFO [org.teiid.PROCESSOR] (New I/O server worker #2-1) Clearing
the resultset cache for vdb
PREVIEW_70a7a0cb-5c46-4589-aa1c-9018517e0c0f_FinancialsDemo_project.1
2012-08-15 15:10:29,896 INFO [STDOUT] (New I/O server worker #2-1)
--
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: