[JBoss JIRA] (TEIID-4303) Insert into temporary table fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4303?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4303:
---------------------------------------
So data is being retrieved, then the transaction gets into the cancelled state via a timeout:
Abort of action id 0:ffff7f000101:2f4a8c3a:576d4165:72fc invoked while multiple threads active within it.
And then the insert fails. So the question is if the timeout is expected. The default timeout is 5 minutes - http://www.mastertheboss.com/jboss-server/jboss-configuration/configuring...
> Insert into temporary table fails
> ---------------------------------
>
> Key: TEIID-4303
> URL: https://issues.jboss.org/browse/TEIID-4303
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.0
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Attachments: debugplan.txt
>
>
> When executing a insert query in a temporary table the execution fails with the following error:
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed execution
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed connection
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END SRC COMMAND: endTime=2016-06-28 08:54:35.7 requestID=3bZw8VxEr4t7.26 sourceCommandID=4 executionID=30 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > modelName=iziswh translatorName=sybase sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security finalRowCount=21504 cpuTime(ns)=120503397
> 2016-06-28 08:54:35,701 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ERROR USER COMMAND: endTime=2016-06-28 08:54:35.701 requestID=3bZw8VxEr4t7.26 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=null
> 2016-06-28 08:54:35,701 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 TEIID30020 Processing exception for request 3bZw8VxEr4t7.26 'TEIID30223 javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state'. Originally TeiidProcessingException TransactionImple.java:396. Enable more detailed logging to see the entire stacktrace.
> 2016-06-28 08:54:35,701 WARN [com.arjuna.ats.arjuna] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ARJUNA012077: Abort called on already aborted atomic action 0:ffff7f000101:2f4a8c3a:576d4165:72fc
> 2016-06-28 08:54:35,702 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END USER COMMAND: endTime=2016-06-28 08:54:35.702 requestID=3bZw8VxEr4t7.26 txID=null sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (TEIID-4303) Insert into temporary table fails
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-4303?page=com.atlassian.jira.plugin... ]
Bram Gadeyne commented on TEIID-4303:
-------------------------------------
There are several:
1)
2016-06-28 08:51:58,811 DEBUG [org.teiid.SECURITY] (NIO1) Keep-alive ping received for session: 3bZw8VxEr4t7
2016-06-28 08:52:31,721 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff7f000101:2f4a8c3a:576d4165:72fc in state RUN
2016-06-28 08:52:31,722 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 2) ARJUNA012095: Abort of action id 0:ffff7f000101:2f4a8c3a:576d4165:72fc invoked while multiple threads active within it.
2016-06-28 08:52:31,722 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 2) ARJUNA012108: CheckedAction::check - atomic action 0:ffff7f000101:2f4a8c3a:576d4165:72fc aborting with 1 threads active!
2016-06-28 08:52:32,221 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff7f000101:2f4a8c3a:576d4165:72fc in state CANCEL
2016-06-28 08:52:32,222 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012378: ReaperElement appears to be wedged: sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
java.util.concurrent.locks.ReentrantLock$FairSync.lock(ReentrantLock.java:224)
java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.lock(BaseWrapperManagedConnection.java:378)
org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:290)
org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118)
com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:318)
com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2993)
com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2972)
com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1675)
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127)
com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215)
com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:381)
com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:78)
2016-06-28 08:52:32,722 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff7f000101:2f4a8c3a:576d4165:72fc in state CANCEL_INTERRUPTED
2016-06-28 08:52:32,722 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012120: TransactionReaper::check worker Thread[Transaction Reaper Worker 2,5,main] not responding to interrupt when cancelling TX 0:ffff7f000101:2f4a8c3a:576d4165:72fc -- worker marked as zombie and TX scheduled for mark-as-rollback
2016-06-28 08:52:32,723 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012110: TransactionReaper::check successfuly marked TX 0:ffff7f000101:2f4a8c3a:576d4165:72fc as rollback only
2)
doCancellations worker while retrieving data
2016-06-28 08:54:35,563 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Processing MORE request
2016-06-28 08:54:35,563 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Getting results from connector
2016-06-28 08:54:35,564 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Obtained results from connector, current row count: 3072
2016-06-28 08:54:35,564 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Processing MORE request
2016-06-28 08:54:35,565 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Getting results from connector
2016-06-28 08:54:35,565 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 2) ARJUNA012113: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 2,5,main] missed interrupt when cancelling TX 0:ffff7f000101:2f4a8c3a:576d4165:72fc -- exiting as zombie (zombie count decremented to 0)
2016-06-28 08:54:35,570 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Obtained results from connector, current row count: 3328
2016-06-28 08:54:35,570 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Processing MORE request
2016-06-28 08:54:35,570 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Getting results from connector
2016-06-28 08:54:35,571 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Obtained results from connector, current row count: 3584
2016-06-28 08:54:35,571 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Processing MORE request
2016-06-28 08:54:35,571 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Getting results from connector
2016-06-28 08:54:35,572 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Obtained results from connector, current row count: 3840
> Insert into temporary table fails
> ---------------------------------
>
> Key: TEIID-4303
> URL: https://issues.jboss.org/browse/TEIID-4303
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.0
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Attachments: debugplan.txt
>
>
> When executing a insert query in a temporary table the execution fails with the following error:
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed execution
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed connection
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END SRC COMMAND: endTime=2016-06-28 08:54:35.7 requestID=3bZw8VxEr4t7.26 sourceCommandID=4 executionID=30 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > modelName=iziswh translatorName=sybase sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security finalRowCount=21504 cpuTime(ns)=120503397
> 2016-06-28 08:54:35,701 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ERROR USER COMMAND: endTime=2016-06-28 08:54:35.701 requestID=3bZw8VxEr4t7.26 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=null
> 2016-06-28 08:54:35,701 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 TEIID30020 Processing exception for request 3bZw8VxEr4t7.26 'TEIID30223 javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state'. Originally TeiidProcessingException TransactionImple.java:396. Enable more detailed logging to see the entire stacktrace.
> 2016-06-28 08:54:35,701 WARN [com.arjuna.ats.arjuna] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ARJUNA012077: Abort called on already aborted atomic action 0:ffff7f000101:2f4a8c3a:576d4165:72fc
> 2016-06-28 08:54:35,702 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END USER COMMAND: endTime=2016-06-28 08:54:35.702 requestID=3bZw8VxEr4t7.26 txID=null sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (TEIID-4303) Insert into temporary table fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4303?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4303:
---------------------------------------
The exception reported is "'TEIID30223 javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state'" which means that the transaction had already been aborted by the time that the temp table logic was trying to enlist itself. Are there any other logs or indications of why the transaction has already been aborted?
> Insert into temporary table fails
> ---------------------------------
>
> Key: TEIID-4303
> URL: https://issues.jboss.org/browse/TEIID-4303
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.0
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Attachments: debugplan.txt
>
>
> When executing a insert query in a temporary table the execution fails with the following error:
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed execution
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 3bZw8VxEr4t7.26.4.30 Closed connection
> 2016-06-28 08:54:35,700 DEBUG [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END SRC COMMAND: endTime=2016-06-28 08:54:35.7 requestID=3bZw8VxEr4t7.26 sourceCommandID=4 executionID=30 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > modelName=iziswh translatorName=sybase sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security finalRowCount=21504 cpuTime(ns)=120503397
> 2016-06-28 08:54:35,701 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ERROR USER COMMAND: endTime=2016-06-28 08:54:35.701 requestID=3bZw8VxEr4t7.26 txID=TransactionImple < ac, BasicAction: 0:ffff7f000101:2f4a8c3a:576d4165:72fc status: ActionStatus.ABORTED > sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=null
> 2016-06-28 08:54:35,701 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 TEIID30020 Processing exception for request 3bZw8VxEr4t7.26 'TEIID30223 javax.transaction.RollbackException: ARJUNA016083: Can't register synchronization because the transaction is in aborted state'. Originally TeiidProcessingException TransactionImple.java:396. Enable more detailed logging to see the entire stacktrace.
> 2016-06-28 08:54:35,701 WARN [com.arjuna.ats.arjuna] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 ARJUNA012077: Abort called on already aborted atomic action 0:ffff7f000101:2f4a8c3a:576d4165:72fc
> 2016-06-28 08:54:35,702 INFO [org.teiid.COMMAND_LOG] (Worker12_QueryProcessorQueue243) 3bZw8VxEr4t7 END USER COMMAND: endTime=2016-06-28 08:54:35.702 requestID=3bZw8VxEr4t7.26 txID=null sessionID=3bZw8VxEr4t7 principal=veerle@teiid-security vdbName=vdb3 vdbVersion=14 finalRowCount=0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (TEIID-4294) External Materialization MATVIEW_AFTER_LOAD_SCRIPT is not atomic operation
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4294?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-4294:
------------------------------------
[~shawkins]
I reproduced the issue also when using sql server 2012 as xa-datasource with three source native commands separated by semicolon and "teiid_rel:MATVIEW_ONERROR_ACTION" set to 'IGNORE' or 'WAIT':
{code:sql}
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''sp_rename DV_MATVIEWS_MAT_VIEW_STAGE, DV_MATVIEWS_MAT_VIEW_TEMP'');exec Source.native(''sp_rename DV_MATVIEWS_MAT_VIEW, DV_MATVIEWS_MAT_VIEW_STAGE'');exec Source.native(''sp_rename DV_MATVIEWS_MAT_VIEW_temp, DV_MATVIEWS_MAT_VIEW'');',
"teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT'
{code}
Using this datasource:
{code:xml}
<xa-datasource jndi-name="java:/mssql2012-ds" pool-name="mssql2012-ds" enabled="true">
<xa-datasource-property name="ServerName">
db06.mw.lab.eng.bos.redhat.com
</xa-datasource-property>
<xa-datasource-property name="DatabaseName">
dballo06
</xa-datasource-property>
<driver>mssql2012-driver</driver>
<security>
<user-name>dballo06</user-name>
<password>dballo06</password>
</security>
</xa-datasource>
{code}
And driver:
{code:xml}
<driver name="mssql2012-driver" module="mssql2012">
<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
</driver>
{code}
> External Materialization MATVIEW_AFTER_LOAD_SCRIPT is not atomic operation
> --------------------------------------------------------------------------
>
> Key: TEIID-4294
> URL: https://issues.jboss.org/browse/TEIID-4294
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: dv-2016-06-23-mat-view.log
>
>
> Firstly, this issue appears even after *TEIID-4283* fix, and is db independent.
> When during materialized view's loading there is a query on the view performed, timing issues appear. In MATVIEW_AFTER_LOAD_SCRIPT there might be more commands separated by semicolon, but these commands are not performed as a single operation. In specific timing a query on such view might fail when you have a MATVIEW_AFTER_LOAD_SCRIPT like this:
> {code:sql}
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view'');
> {code}
> user might end up querying the view right in the moment, when 'primary' materialized table (dv_matviews_mat_view) was renamed (dv_matviews_mat_view_stage) and thus there's no such table like defined in the materialized view.
> {code:xml}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'IGNORE',
> "teiid_rel:MATVIEW_TTL" 20000)
> AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Then for some queries I get:
> {code:plain}
> 10:40:19,252 WARN [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue130) Connector worker process failed for atomic-request=+k/MyS3sUhQX.14.7.113: org.teiid.translator.jdbc.JDBCExecutionException: 259 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."CUSTOMER_ID", g_0."TOTAL_AMOUNT" FROM "JSTASTNY".dvqe_X_XjdkY_YDV_MATVIEWS_MAT_VIEW AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-5.jar:8.12.5.redhat-5]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364)
> at sun.reflect.GeneratedMethodAccessor158.invoke(Unknown Source) [:1.7.0_79]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy80.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [259]: invalid table name: Could not find table/view DVQE_X_XJDKY_YDV_MATVIEWS_MAT_VIEW in schema JSTASTNY: line 1 col 62 (at pos 61)
> at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:345)
> at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:185)
> at com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:100)
> at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1130)
> at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:877)
> at com.sap.db.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:410)
> at com.sap.db.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:266)
> at com.sap.db.jdbc.CallableStatementSapDB.executeQuery(CallableStatementSapDB.java:756)
> at com.sap.db.jdbc.trace.PreparedStatement.executeQuery(PreparedStatement.java:161)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.5.redhat-5.jar:8.12.5.redhat-5]
> ... 17 more
> {code}
> From the logs it seems that the after load script has completed, but probably not in the source db. In logs just before the exception I see:
> {code:plain}
> 12:34:59,247 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) Source-specific command: RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view
> 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Executed command
> 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Processing MORE request
> 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Getting results from connector
> 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Obtained last batch, total row count: 1
> 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Remove State
> 12:34:59,664 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Processing Close : EXEC Source.native('RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view')
> {code}
> I attached the logs to this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (TEIID-3781) Queries are not killed even if the client sends a cancel request
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3781?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3781:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1315378|https://bugzilla.redhat.com/show_bug.cgi?id=1315378] from ON_QA to VERIFIED
> Queries are not killed even if the client sends a cancel request
> ----------------------------------------------------------------
>
> Key: TEIID-3781
> URL: https://issues.jboss.org/browse/TEIID-3781
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.0
> Reporter: Salvatore R
> Assignee: Steven Hawkins
> Fix For: 8.12.1, 8.13
>
>
> I have different behaviors when I try to cancel the following queries:
> {code:sql}
> SELECT COUNT(*)
> FROM
> (SELECT * FROM my.address) as x1,
> (SELECT * FROM my.address) as y1
> {code}
> and
> {code:sql}
> SELECT COUNT(*)
> FROM
> (SELECT * FROM my.address limit 10000) as x1,
> (SELECT * FROM my.address limit 10000) as y1
> {code}
> where "my.address" is a table with around 20000 rows in MySQL.
> The first query is immediately cancelled but the second one continues to run until the end and it is never killed.
> Looking at the generated plans, the main difference is that the first query is fully pushed down to MySQL while the second one is not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months