[JBoss JIRA] (TEIID-4782) Change framework to catch RutineException from translator/connector
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4782?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-4782:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Change framework to catch RutineException from translator/connector
> -------------------------------------------------------------------
>
> Key: TEIID-4782
> URL: https://issues.jboss.org/browse/TEIID-4782
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 9.3
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> Discussion:
> Generally the connector/engine logic should be responsible for handling whatever exception is thrown. For example ConnectorWorkItem and DataTeirTupleSource do intercept RuntimeExceptions, but rethrows them. We may want to instead convert them into Processing exceptions as the ConnectorWorkItem level.
> ----- Original Message -----
> > With Resource-adapters, the drivers to connect to some of these data sources
> > are not standard. And because of that, just like with JDG, its probable
> > that other drivers will be throwing unexpected exceptions when those data
> > sources are scaled up and down. I know the supporting of other RA data
> > sources is probably not real close, but would it be pro-active to look at
> > possible RA's and that may need to have try/catches added?
> >
> > Van
> >
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (TEIID-4782) Change framework to catch RutineException from translator/connector
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4782?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-4782:
--------------------------------
Parent: TEIID-4779
Issue Type: Sub-task (was: Enhancement)
> Change framework to catch RutineException from translator/connector
> -------------------------------------------------------------------
>
> Key: TEIID-4782
> URL: https://issues.jboss.org/browse/TEIID-4782
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 9.3
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Discussion:
> Generally the connector/engine logic should be responsible for handling whatever exception is thrown. For example ConnectorWorkItem and DataTeirTupleSource do intercept RuntimeExceptions, but rethrows them. We may want to instead convert them into Processing exceptions as the ConnectorWorkItem level.
> ----- Original Message -----
> > With Resource-adapters, the drivers to connect to some of these data sources
> > are not standard. And because of that, just like with JDG, its probable
> > that other drivers will be throwing unexpected exceptions when those data
> > sources are scaled up and down. I know the supporting of other RA data
> > sources is probably not real close, but would it be pro-active to look at
> > possible RA's and that may need to have try/catches added?
> >
> > Van
> >
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (TEIID-4782) Change framework to catch RutineException from translator/connector
by Van Halbert (JIRA)
Van Halbert created TEIID-4782:
----------------------------------
Summary: Change framework to catch RutineException from translator/connector
Key: TEIID-4782
URL: https://issues.jboss.org/browse/TEIID-4782
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 9.3
Reporter: Van Halbert
Assignee: Steven Hawkins
Discussion:
Generally the connector/engine logic should be responsible for handling whatever exception is thrown. For example ConnectorWorkItem and DataTeirTupleSource do intercept RuntimeExceptions, but rethrows them. We may want to instead convert them into Processing exceptions as the ConnectorWorkItem level.
----- Original Message -----
> With Resource-adapters, the drivers to connect to some of these data sources
> are not standard. And because of that, just like with JDG, its probable
> that other drivers will be throwing unexpected exceptions when those data
> sources are scaled up and down. I know the supporting of other RA data
> sources is probably not real close, but would it be pro-active to look at
> possible RA's and that may need to have try/catches added?
>
> Van
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (TEIID-4519) JDG prevent execution of delete or update on child objects
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4519?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4519:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1385644|https://bugzilla.redhat.com/show_bug.cgi?id=1385644] from VERIFIED to CLOSED
> JDG prevent execution of delete or update on child objects
> ----------------------------------------------------------
>
> Key: TEIID-4519
> URL: https://issues.jboss.org/browse/TEIID-4519
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.7.6_3
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Priority: Critical
> Fix For: 8.12.7.6_3
>
>
> When using JDG and complex pojos, delete query issued against child tables end with error.
> * 1-1 relation:
> When deleting a child object, whole parent object is deleted
> * 1-n relation:
> An exception is thrown:
> {code:plain}
> 13:31:28,926 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue91) Connector worker process failed for atomic-request=rKsoeHUfbaAW.21.0.21: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method number on class java.util.ArrayList.
> at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:388) [translator-object-8.12.6.6_3.jar:8.12.6.6_3]
> at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:137) [translator-object-8.12.6.6_3.jar:8.12.6.6_3]
> at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.6.6_3.jar:8.12.6.6_3]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) [:1.8.0_102]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at com.sun.proxy.$Proxy81.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_102]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.6.6_3-redhat-1.jar:8.12.6.6_3-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_102]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102]
> Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method number on class java.util.ArrayList.
> at org.teiid.translator.object.ObjectScriptEngine$1.eval(ObjectScriptEngine.java:144) [translator-object-8.12.6.6_3.jar:8.12.6.6_3]
> at org.teiid.translator.object.ObjectUpdateExecution.handleDelete(ObjectUpdateExecution.java:372) [translator-object-8.12.6.6_3.jar:8.12.6.6_3]
> ... 20 more
> {code}
> These two cases should be handled. Given the lack of DELETE support, all the DELETE queries on child entities should throw exception instead.
> The DELETE on parent should be enabled though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (TEIID-4781) upgrade MongoDB Java Driver
by Kylin Soong (JIRA)
Kylin Soong created TEIID-4781:
----------------------------------
Summary: upgrade MongoDB Java Driver
Key: TEIID-4781
URL: https://issues.jboss.org/browse/TEIID-4781
Project: Teiid
Issue Type: Task
Components: Misc. Connectors
Affects Versions: 9.3
Reporter: Kylin Soong
Assignee: Kylin Soong
Fix For: 9.3
There are five 3.x version java driver for now, we currently still use 2.13.1, probably we need upgrade the driver to a later one.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (TEIID-4336) Errors in logs during server shutdown
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4336?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4336:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1357529|https://bugzilla.redhat.com/show_bug.cgi?id=1357529] from NEW to CLOSED
> Errors in logs during server shutdown
> -------------------------------------
>
> Key: TEIID-4336
> URL: https://issues.jboss.org/browse/TEIID-4336
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.0, 9.0.2
>
> Attachments: server.log
>
>
> When using materialization and user shuts down the server without disabling the vdb with materialized view defined a few exceptions appear in the server logs.
> I attached full server.log to this issue.
> {code:plain}
> 08:05:50,764 ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue626) Connector worker process failed for atomic-request=RsQyJH143A1D.0.0.953: java.lang.NullPointerException
> at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:196) [translator-jdbc-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:121) [translator-jdbc-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364)
> at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) [:1.8.0_92]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy45.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:142)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92)
> at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:608)
> at org.teiid.query.processor.proc.LoopInstruction.testCondition(LoopInstruction.java:108)
> at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:379)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:298)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:270)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274)
> 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:1142) [rt.jar:1.8.0_92]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
> {code}
> and
> {code:plain}
> 8:05:50,797 WARN [org.teiid.PROCESSOR.MATVIEWS] (MSC service thread 1-2) org.teiid.core.TeiidException: java.sql.SQLException: org.teiid.core.TeiidException
> at org.teiid.runtime.MaterializationManager.executeQuery(MaterializationManager.java:349) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.runtime.MaterializationManager$1.process(MaterializationManager.java:101) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.runtime.MaterializationManager.doMaterializationActions(MaterializationManager.java:199) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.runtime.MaterializationManager.beforeRemove(MaterializationManager.java:90) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.deployers.VDBRepository.notifyBeforeRemove(VDBRepository.java:394) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.deployers.VDBRepository.removeVDB(VDBRepository.java:264) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.deployers.VDBRepository.removeVDB(VDBRepository.java:260) [teiid-runtime-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.jboss.VDBService.cleanup(VDBService.java:264) [teiid-jboss-integration-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.jboss.VDBService.stop(VDBService.java:276) [teiid-jboss-integration-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2088) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2049) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
> Caused by: org.teiid.core.TeiidException
> at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:196) [teiid-client-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:1088) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.RequestWorkItem.close(RequestWorkItem.java:578) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:374) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> ... 3 more
> Caused by: java.lang.NullPointerException
> at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:196)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:121)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source) [:1.8.0_92]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at com.sun.proxy.$Proxy45.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:142) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:608) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.proc.LoopInstruction.testCondition(LoopInstruction.java:108) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:379) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:298) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:270) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.5.redhat-7.jar:8.12.5.redhat-7]
> ... 8 more
> {code}
> and in the end:
> {code:plain}
> 08:05:50,818 WARN [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000004: Failure during stop of service jboss.teiid.vdb.saphana.1: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.teiid.jboss.DQPCoreService$1.removed(DQPCoreService.java:117)
> at org.teiid.deployers.VDBRepository.notifyRemove(VDBRepository.java:387)
> at org.teiid.deployers.VDBRepository.removeVDB(VDBRepository.java:271)
> at org.teiid.deployers.VDBRepository.removeVDB(VDBRepository.java:260)
> at org.teiid.jboss.VDBService.cleanup(VDBService.java:264)
> at org.teiid.jboss.VDBService.stop(VDBService.java:276)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2088) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2049) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month