[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3070:
----------------------------------
Security: Public (was: Red Hat Internal)
Converting to a public issue to reference from cases as needed.
> 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: Steven Hawkins
>
> 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.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3073) Tableau Connection Issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3073?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3073:
----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Tableau Connection Issues
> -------------------------
>
> Key: TEIID-3073
> URL: https://issues.jboss.org/browse/TEIID-3073
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ODBC, Server
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> It has been reported that using Tableu with Teiid ODBC port show the following errors. These need to be investigated and fixed
> {code}
> This ODBC driver does not support important capabilities used by Tableau.
> This unsupported function is required for relative date filters: The date part named 'week' for the date function: DATETRUNC(date_part, date, [start_of_week])
> -----
> Tableau identified the following warnings for the ODBC data source named 'streamyx_sales (streamyx_sales.streamyx_sales) (TMJDV)':
> This aggregation is unsupported: Attribute
> This aggregation is unsupported: Std. Dev
> This aggregation is unsupported: Std. Dev (Pop.)
> This aggregation is unsupported: Trunc Week Number
> This aggregation is unsupported: Variance
> This aggregation is unsupported: Variance (Pop.)
> This function is unsupported: % with parameter types 'integer, integer'
> This function is unsupported: ABS(number) with parameter types 'float'
> This function is unsupported: ABS(number) with parameter types 'integer'
> This function is unsupported: ACOS(number) with parameter types 'float'
> This function is unsupported: ASCII(string) with parameter types 'string'
> This function is unsupported: ASIN(number) with parameter types 'float'
> This function is unsupported: ATAN(number) with parameter types 'float'
> This function is unsupported: ATAN2(y number, x number) with parameter types 'float, float'
> This function is unsupported: CHAR(integer) with parameter types 'float'
> This function is unsupported: CHAR(integer) with parameter types 'integer'
> This function is unsupported: COS(angle) with parameter types 'float'
> This function is unsupported: COT(angle) with parameter types 'float'
> This function is unsupported: DATEPART_DAYOFWEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATEPART_WEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATETIME with parameter types 'integer'
> This function is unsupported: DEGREES(number) with parameter types 'float'
> This function is unsupported: EXP(number) with parameter types 'float'
> This function is unsupported: LN with parameter types 'float'
> This function is unsupported: LN(number) with parameter types 'float'
> This function is unsupported: LOG with parameter types 'float'
> This function is unsupported: LOG(number, [base]) with parameter types 'float'
> This function is unsupported: PI()
> This function is unsupported: POWER with parameter types 'float, integer'
> This function is unsupported: POWER with parameter types 'integer, integer'
> This function is unsupported: POWER(number,power) with parameter types 'float, integer'
> This function is unsupported: POWER(number,power) with parameter types 'integer, integer'
> This function is unsupported: RADIANS(number) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float, integer'
> This function is unsupported: SIGN(number) with parameter types 'float'
> This function is unsupported: SIN(angle) with parameter types 'float'
> This function is unsupported: SPACE with parameter types 'float'
> This function is unsupported: SPACE(number) with parameter types 'integer'
> This function is unsupported: SQRT(number) with parameter types 'float'
> This function is unsupported: SQUARE with parameter types 'float'
> This function is unsupported: TAN(angle) with parameter types 'float'
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This is unsupported: SELECT ... INTO
> This is unsupported: Temporary tables
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3074) NPE When using External Materialization management is use
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3074?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3074:
---------------------------------------
If close is coming before next, then this error is effectively swallowed correct?
I don't really see a path by which this can occur though as unless a non-processing thread was used to make the close call. What other specifics do you have such as is it the subquery or the other source access that is seeing the exception, etc.?
> NPE When using External Materialization management is use
> ---------------------------------------------------------
>
> Key: TEIID-3074
> URL: https://issues.jboss.org/browse/TEIID-3074
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Attachments: debug_plan.txt, solr-integration-with-matview-vdb.xml
>
>
> When I was issuing query that has externalized materialization with management option to true, I am seeing NPE. Tried to see why NPE is occurring was not able to figure out (yet)
> {code}
> 14:37:50,269 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8477) 0z97J5OWq7x9 Connector worker process failed for atomic-request=0z97J5OWq7x9.7.1.4220: java.lang.NullPointerException
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:385) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:203) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ]
Van Halbert edited comment on TEIID-3091 at 8/18/14 2:05 PM:
-------------------------------------------------------------
No, the image shows that row 1 has the column headers in the results. The 1st row should start with row 2 in the file (by passing the column headers), irrespective if LIMIT clause is used.
was (Author: van.halbert):
No, the image shows that row 1 has the column headers in the results. The 1st row should start with row 2 in the file (by passing the column headers).
> Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
> -----------------------------------------------------------------
>
> Key: TEIID-3091
> URL: https://issues.jboss.org/browse/TEIID-3091
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Attachments: excel_row_number_issue.tiff
>
>
> The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
> {code}
> <model name="OtherHoldings">
> <property name="importer.headerRowNumber" value="1"/>
> <property name="importer.ExcelFileName" value="otherholdings.xls"/>
> <source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> ]]> </metadata>
> </model>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3091) Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3091?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3091:
------------------------------------
No, the image shows that row 1 has the column headers in the results. The 1st row should start with row 2 in the file (by passing the column headers).
> Excel translator issue: FIRST_DATA_ROW_NUMBER option not working
> -----------------------------------------------------------------
>
> Key: TEIID-3091
> URL: https://issues.jboss.org/browse/TEIID-3091
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Attachments: excel_row_number_issue.tiff
>
>
> The FIRST_DATA_ROW_NUMBER option not working, seeing the first row in the results, when using the following dynamic VDB definition:
> {code}
> <model name="OtherHoldings">
> <property name="importer.headerRowNumber" value="1"/>
> <property name="importer.ExcelFileName" value="otherholdings.xls"/>
> <source name="excelconnector" translator-name="excel" connection-jndi-name="java:/excel-file"/>
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel;
> CREATE FOREIGN TABLE Sheet1 (
> ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'),
> FirstName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'),
> LastName string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'),
> Age string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'),
> CONSTRAINT PK0 PRIMARY KEY(ROW_ID)
> ) OPTIONS ("teiid_excel:FILE" 'otherholdings.xls', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2');
> ]]> </metadata>
> </model>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months