[JBoss JIRA] (TEIID-4775) When using external materialization, after transaction timeout, LoadState continues to be LOADING
10:38 a.m.
[
https://issues.jboss.org/browse/TEIID-4775?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4775:
-------------------------------------
The situation can also occur if any of the resource-adapter, translator or data source
throw a runtime exception (transaction rollback exception is also runtime exception) while
processing a procedure block. In this case, the exception is raised above the exception
block in the procedure and never executes any exception handling defined in the
procedure.
Per [~shawkins] I think the rationale was that it is unexpected - but it does logically
apply to the block, so it should be handled - it's just that it will mask the real
exception
So, the solution is to let the procedure handle the all exceptions, but they can choose to
log the message to keep track of the original exception instead of swallowing it.
When using external materialization, after transaction timeout,
LoadState continues to be LOADING
-------------------------------------------------------------------------------------------------
Key: TEIID-4775
URL: https://issues.jboss.org/browse/TEIID-4775
Project: Teiid
Issue Type: Sub-task
Components: Server
Affects Versions: 8.7
Environment: * CentOs 7
* Teiid 9.1.2
* Wildfly 10
Reporter: Pedro Inácio
Assignee: Ramesh Reddy
Fix For: 9.3
For some unknown reason, sometimes a materialized view takes more time to finish the
load/update than the one defined in transaction timeout (300 seconds is the default value,
and we have configured 600 seconds to try to solve the problem).
The transaction reaper will kill the update transaction. The _LoadState_ in _status_
table will be *LOADING*.
Any subsequent try to update the view will fail, since the system reads the state as
being *LOADING* even if the system is not currently updating it.
Example log next.
The update took too long (more than 10 minutes [defined transaction timeout]):
{code:batch}
2017-02-17 16:10:44,487 INFO [org.teiid.COMMAND_LOG] (NIO6) gZueFR0aNjgi START
USER COMMAND: startTime=2017-02-17 16:10:44.487 requestID=gZueFR0aNjgi.11
txID=null sessionID=gZueFR0aNjgi applicationName=JDBC principal=manel
vdbName=CountryServiceListVDB vdbVersion=1 sql={call SYSADMIN.loadMatView(?, ?)}
2017-02-17 16:20:44,528 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117:
TransactionReaper::check timeout for TX 0:ffff0a080174:21ddbdf0:58a71a32:cb in state RUN
2017-02-17 16:20:44,564 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0)
ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker
0,5,main] successfully canceled TX 0:ffff0a080174:21ddbdf0:58a71a32:cb
{code}
Next I tried to update the view:
{code:batch}
2017-02-17 16:29:21,272 INFO [org.teiid.COMMAND_LOG] (NIO2) E1xyKpChGKvC START
USER COMMAND: startTime=2017-02-17 16:29:21.272 requestID=E1xyKpChGKvC.7
txID=null sessionID=E1xyKpChGKvC applicationName=JDBC principal=manel
vdbName=CountryServiceListVDB vdbVersion=1 sql=EXECUTE
SYSADMIN.loadMatView('CountryServiceListCalculatedRaw','country_service_list_calculated_raw')
2017-02-17 16:29:21,391 INFO [org.teiid.COMMAND_LOG] (Worker25_QueryProcessorQueue18136)
E1xyKpChGKvC END USER COMMAND: endTime=2017-02-17 16:29:21.391
requestID=E1xyKpChGKvC.7 txID=null sessionID=E1xyKpChGKvC principal=manel
vdbName=CountryServiceListVDB vdbVersion=1 finalRowCount=1
{code}
And nothing happened.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
2869
days inactive
2869
days old
0 comments
1 participants
participants (1)
-
Ramesh Reddy (JIRA)