[JBoss JIRA] (TEIID-3116) Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3116?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3116:
---------------------------------------
This is expected behavior. If no database version is set on a translator that automatically determines capabilities, then it will not allow planning to proceed. So if you expect the source to be unavailable, then you should manually set the database version.
> Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-3116
> URL: https://issues.jboss.org/browse/TEIID-3116
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
>
> Description of problem:
> Querying a vdb-table which is formed as union of two tables from different datasources. Even though "set partialresultsmode true" is run as initial query, instead of retreiving 0 rows from a datasources that is down, exception is promoted.
> Version-Release number of selected component (if applicable):
> DV 6.1 ER1
> How reproducible:
> Every time
> Steps to Reproduce:
> 1. Define one valid and one invalid datasource(invalid connection-url).
> 2. Create vdb which maps tables from both datasources.
> 3. Set partialresultsmode to true
> 4. Execute query on the given vdb-table
> Actual results:
> TeiidSQLException
> TEIID30498 Remote org.teiid.api.exception.query.QueryPlannerException: TEIID30498 Capabilities for ORBQT were not avaialable. The command could not be planned properly.
> Expected results:
> 0 rows from invalid datasource.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3117) NullPointerException while creating source model from Excel table
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-3117?page=com.atlassian.jira.plugin... ]
Juraj Duráni updated TEIID-3117:
--------------------------------
Attachment: ExcelDynamic-vdb.xml
Server.log
smalla.xlsx
smalla_raw.xlsx
Excel files, dynamic vdb, exception
> NullPointerException while creating source model from Excel table
> -----------------------------------------------------------------
>
> Key: TEIID-3117
> URL: https://issues.jboss.org/browse/TEIID-3117
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Environment: Fedora 20, data virtualization 6.1.0.ER1
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Attachments: ExcelDynamic-vdb.xml, Server.log, smalla.xlsx, smalla_raw.xlsx
>
>
> I am trying to create source model from Excel file (.xlsx). When I set property "Header Row Number" to 1 (using Teiid Designer), creating ends with NullPointerException. Setting "Header Row Number" to 0 executes with no problems.
> Same problem (and same exception) with dynamic VDB (only with <property name="importer.headerRowNumber" value="1"/>).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3117) NullPointerException while creating source model from Excel table
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3117:
-----------------------------------
Summary: NullPointerException while creating source model from Excel table
Key: TEIID-3117
URL: https://issues.jboss.org/browse/TEIID-3117
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7
Environment: Fedora 20, data virtualization 6.1.0.ER1
Reporter: Juraj Duráni
Assignee: Steven Hawkins
I am trying to create source model from Excel file (.xlsx). When I set property "Header Row Number" to 1 (using Teiid Designer), creating ends with NullPointerException. Setting "Header Row Number" to 0 executes with no problems.
Same problem (and same exception) with dynamic VDB (only with <property name="importer.headerRowNumber" value="1"/>).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3116) Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3116?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3116:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1138679
> Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-3116
> URL: https://issues.jboss.org/browse/TEIID-3116
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
>
> Description of problem:
> Querying a vdb-table which is formed as union of two tables from different datasources. Even though "set partialresultsmode true" is run as initial query, instead of retreiving 0 rows from a datasources that is down, exception is promoted.
> Version-Release number of selected component (if applicable):
> DV 6.1 ER1
> How reproducible:
> Every time
> Steps to Reproduce:
> 1. Define one valid and one invalid datasource(invalid connection-url).
> 2. Create vdb which maps tables from both datasources.
> 3. Set partialresultsmode to true
> 4. Execute query on the given vdb-table
> Actual results:
> TeiidSQLException
> TEIID30498 Remote org.teiid.api.exception.query.QueryPlannerException: TEIID30498 Capabilities for ORBQT were not avaialable. The command could not be planned properly.
> Expected results:
> 0 rows from invalid datasource.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3116) Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)
by Van Halbert (JIRA)
Van Halbert created TEIID-3116:
----------------------------------
Summary: Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)
Key: TEIID-3116
URL: https://issues.jboss.org/browse/TEIID-3116
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Critical
Description of problem:
Querying a vdb-table which is formed as union of two tables from different datasources. Even though "set partialresultsmode true" is run as initial query, instead of retreiving 0 rows from a datasources that is down, exception is promoted.
Version-Release number of selected component (if applicable):
DV 6.1 ER1
How reproducible:
Every time
Steps to Reproduce:
1. Define one valid and one invalid datasource(invalid connection-url).
2. Create vdb which maps tables from both datasources.
3. Set partialresultsmode to true
4. Execute query on the given vdb-table
Actual results:
TeiidSQLException
TEIID30498 Remote org.teiid.api.exception.query.QueryPlannerException: TEIID30498 Capabilities for ORBQT were not avaialable. The command could not be planned properly.
Expected results:
0 rows from invalid datasource.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3115) Invalid Query With OrderBy in SubQuery Table
by Joseph CHIDIAC (JIRA)
Joseph CHIDIAC created TEIID-3115:
-------------------------------------
Summary: Invalid Query With OrderBy in SubQuery Table
Key: TEIID-3115
URL: https://issues.jboss.org/browse/TEIID-3115
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.8
Reporter: Joseph CHIDIAC
Assignee: Steven Hawkins
Fix For: 8.8
Hi, I'm using Teiid Embedded Server , i tried to execute the Following query :
SELECT jiraissue.issuetype
FROM imOrganizationjiraissue jiraissue
LEFT OUTER JOIN
(SELECT jiraissue_sub.issuetype AS jiraissue_issuetype,
AVG(
TIMESTAMPDIFF(SQL_TSI_DAY,
jiraissue_sub.CREATED,
jiraissue_sub.RESOLUTIONDATE))
AS CalculatedField
FROM jiraissue jiraissue_sub
GROUP BY jiraissue_sub.issuetype
ORDER BY AVG(
TIMESTAMPDIFF(SQL_TSI_DAY,
jiraissue_sub.CREATED,
jiraissue_sub.RESOLUTIONDATE)) ASC
LIMIT 2) j_Sub
ON jiraissue.issuetype = j_Sub.jiraissue_issuetype
i verified the query sent to the JDBC [JDBCQueryExecution.java]
SELECT g_0.issuetype
FROM JIRADB.dbo.jiraissue g_0
LEFT OUTER JOIN (
SELECT TOP 2 g_1.issuetype AS c_0
FROM JIRADB.dbo.jiraissue g_1
GROUP BY g_1.issuetype
ORDER BY anon_grp0.agg0
) v_0
ON g_0.issuetype = v_0.c_0
i got the following exception :
java.sql.SQLException: The multi-part identifier "anon_grp0.agg0" could not be bound
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Devesh Mishra updated TEIID-3106:
---------------------------------
Attachment: LrfuEvictionQueue.java
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java, BufferManagerImpl.java, CacheKey_Loog.patch, cpu monitoring.docx, dump.zip, in_local.docx, LrfuEvictionQueue.java, LrfuEvictionQueue.patch, non_high_cpu.docx
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Devesh Mishra commented on TEIID-3106:
--------------------------------------
Patch failed. I could not merge it automatically but did it manually (and guess accurately). Attaching the merged LrfuEvictionQueue for your reference. Attaching the complete log (from start) - chopped off the loop.
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java, BufferManagerImpl.java, CacheKey_Loog.patch, cpu monitoring.docx, dump.zip, in_local.docx, LrfuEvictionQueue.patch, non_high_cpu.docx
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ]
Kylin Soong reassigned TEIID-3070:
----------------------------------
Assignee: Kylin Soong (was: Steven Hawkins)
> Netty worker threads cause system high cpu
> ------------------------------------------
>
> Key: TEIID-3070
> URL: https://issues.jboss.org/browse/TEIID-3070
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7
> Environment: JDV 6.1.0.DR2
> JDV 6.0
> Reporter: Kylin Soong
> Assignee: Kylin Soong
>
> I have hit this issue many times in deploying a VDB to JDV, All CPU be used by netty worker threads:
> ~~~
> "New I/O worker #3" daemon prio=10 tid=0x00007fc71c0d2000 nid=0x320b runnable [0x00007fc7074f3000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
> - locked <0x00000000c42b4318> (a sun.nio.ch.Util$2)
> - locked <0x00000000c42b4328> (a java.util.Collections$UnmodifiableSet)
> - locked <0x00000000c42b42d0> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
> at org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:64)
> ~~~
> Seems this is a exist netty issue, search "jboss netty high cpu" via google we can get lots of result.
> Below link have detailed depiction about this issue;
> https://github.com/kylinsoong/teiid-samples/tree/master/highcpu
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3114) Add an option to not normalize salesforce names
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3114?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3114.
-----------------------------------
Resolution: Done
Added a normalize names property that can be set to false to not perform the normalization.
> Add an option to not normalize salesforce names
> -----------------------------------------------
>
> Key: TEIID-3114
> URL: https://issues.jboss.org/browse/TEIID-3114
> Project: Teiid
> Issue Type: Enhancement
> Components: Salesforce Connector
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> The normalization process for salesforce names can be non-obvious to follow. The only requirement is that column names don't contain a period - other than that we should have an option to allow the names to be imported more or less undisturbed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months