1 Reply Latest reply on Feb 21, 2013 12:38 PM by shawkins

    VDB not accessible after restarting datasource

    snadji

      Hi,

       

      After restarting the MS SQL server that is being used by the VDB as a datasource, I am not able to access the views in the VDB. I see the exception below in the server.log. The only way I’ve been able to get around this is by setting the datasource to inactive then back to active (redeploying the VDB doesn’t help).

       

      Is there any other workaround? Could the functionality be enhanced so that the translator automatically reconnects?

       

      Thanks

       

      08:54:36,899 WARN  [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue57) Connector worker process failed for atomic-request=9Ei/a665D9n8.7.1.11: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT COUNT(*) FROM "DB1"."dbo"."Project" g_0]

              at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)

              at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:257) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:457) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:177) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:174) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.7.0_10]

              at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.7.0_10]

              at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:118) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:250) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.2.0.Final.jar:8.2.0.Final]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_10]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_10]

              at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_10]

      Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.

              at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)

              at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)

              at com.microsoft.sqlserver.jdbc.SQLServerConnection.prepareStatement(SQLServerConnection.java:2166)

              at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:677)

              at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:663)

              at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:404)

              at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:181)

              at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:82)

        • 1. Re: VDB not accessible after restarting datasource
          shawkins

          > Is there any other workaround? Could the functionality be enhanced so that the translator automatically reconnects?

           

          We see this as more of a pooling issue, than as a Teiid issue.  You'll want to set a test query or just perform a flush of the connection pool on a restart if there is a problem with stale connections.

           

          Steve