[JBoss JIRA] Created: (TEIID-1455) CTC Query Testing - query exception error message not consistant - changes from one run to the next (only happens on RHEL6)
by Warren Gibson (JIRA)
CTC Query Testing - query exception error message not consistant - changes from one run to the next (only happens on RHEL6)
---------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1455
URL: https://issues.jboss.org/browse/TEIID-1455
Project: Teiid
Issue Type: Bug
Components: Integration Tests
Reporter: Warren Gibson
Assignee: Steven Hawkins
Priority: Minor
This problem is not consistent in that it can happen on any source, the number of queries vary, and it eventually goes away with enough executions. I am not sure what is triggering the problem.
As an example I ran the full query suite against Ora11, Ora10, SqlSer2008 in a single test execution and each of them received 41 failures
because the exception error message changed. I then immediately reran the test and this time Ora11, Ora10 and SqlSer2008 all passed but MySql51 had 32 of the same type of failure. I reran the same test a 3rd time and this time everything passed. This has only happened on RHEL6.
Below is an example of one of the failing queries in the latest MySql run. This example has the actual exception from the run and the expected exception. I have also included the exception from the server log and it matches the expected exception.
<?xml version="1.0" encoding="UTF-8"?>
<root>
<queryResults name="RDBMS_Test_Queries_9000_TestQuery255" value="SELECT BQT1.MediumA.ByteNum, BQT2.MediumB.ObjectValue FROM BQT1.MediumA, BQT2.MediumB WHERE BQT1.MediumA.ByteNum = convert(BQT2.MediumB.ObjectValue, byte) AND (BQT1.MediumA.IntKey >= 0 AND BQT1.MediumA.IntKey < 256) AND (BQT2.MediumB.IntKey >= 0 AND BQT2.MediumB.IntKey < 256) ORDER BY BQT1.MediumA.ByteNum">
THIS IS THE ACTUAL EXCEPTION:
<actual_exception>
<exceptionType>TeiidSQLException</exceptionType>
<message>Error trying to execute a statement SELECT BQT1.MediumA.ByteNum, BQT2.MediumB.ObjectValue FROM BQT1.MediumA, BQT2.MediumB WHERE BQT1.MediumA.ByteNum = convert(BQT2.MediumB.ObjectValue, byte) AND (BQT1.MediumA.IntKey >= 0 AND BQT1.MediumA.IntKey < 256) AND (BQT2.MediumB.IntKey >= 0 AND BQT2.MediumB.IntKey < 256) ORDER BY BQT1.MediumA.ByteNum.</message>
<class>org.teiid.jdbc.TeiidSQLException</class>
</actual_exception>
THIS IS THE EXPECTED EXCEPTION
<expected_exception>
<exceptionType>TeiidSQLException</exceptionType>
<message>Error Code:ERR.015.001.0003 Message:Unable to evaluate convert(convert(Source.MEDIUMB.OBJECTVALUE, object), byte): Error Code:ERR.015.001.0003 Message:
Error while evaluating function convert</message>
<class>org.teiid.jdbc.TeiidSQLException</class>
</expected_exception>
</queryResults>
</root>
THIS IS THE EXCEPTION AS STATED IN THE SERVER LOG WHICH MATCHES THE EXPECTED EXCEPTION
2011-01-28 11:17:52,779 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue157992) Processing exception 'Error Code:ERR.015.001.0003 Message:Unable to evaluate convert(convert(Source.MediumB.ObjectValue, object), byte): Error Code:ERR.015.001.0003 Message:Error while evaluating function convert' for request tnuf/C2ODO8c.2685. Exception type org.teiid.api.exception.query.ExpressionEvaluationException thrown from org.teiid.core.types.basic.StringToByteTransform.transformDirect(StringToByteTransform.java:43). Enable more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (TEIID-1474) Add query hint to limit parallel execution of union members
by Howard Abrams (JIRA)
Add query hint to limit parallel execution of union members
-----------------------------------------------------------
Key: TEIID-1474
URL: https://issues.jboss.org/browse/TEIID-1474
Project: Teiid
Issue Type: Feature Request
Reporter: Howard Abrams
Assignee: Steven Hawkins
We would like a new query hint to limit the number of parallel executions of union members. This is useful in two situations:
1. When the queries are expensive, but the overall union contains a limit that is most likely to be fulfilled by the first member of the union
2. When the queries are backed by a common resource which may be overloaded by multiple queries
The addition of a hint would make this manageable by the client; perhaps something like "/*+ parallel=2*/"?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (TEIID-1445) ConcurrentModificationException during the startup of the Server
by Ramesh Reddy (JIRA)
ConcurrentModificationException during the startup of the Server
----------------------------------------------------------------
Key: TEIID-1445
URL: https://issues.jboss.org/browse/TEIID-1445
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.2
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.3
Seems like this is some timing issue.
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at org.teiid.adminapi.impl.ModelMetaData.getValidationErrors(ModelMetaData.java:222)
at org.teiid.adminapi.impl.ModelMetaData.getErrors(ModelMetaData.java:210)
at org.teiid.adminapi.impl.VDBMetaData.getValidityErrors(VDBMetaData.java:249)
at org.teiid.adminapi.impl.VDBMetaData.isValid(VDBMetaData.java:264)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:355)
at org.teiid.deployers.VDBDeployer.access$2(VDBDeployer.java:315)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:308)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months