VDB is not active when war deploys

[jorgecmb]

Hi everyone,

I've been searching an answer for this question for the last week and could find a definitive solution, so I apologize if someone has already answered that.

The problem I am facing is that while the VDB is asynchronously starting up, my application fails deploying - as it tries to connect to the VDB - and only after that the VDB becomes active. Here is what I get on the log:

12:29:47,906 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (ServerService Thread Pool -- 238) JBWEB000289: Servlet dispatcher threw load() exception: org.teiid.core.TeiidProcessingException: TEIID31099 VDB MyVDB.1[my_app{oracle=oracle, oracle, java:/Database}] is not active.  Resubmit your query after loading has completed or after the errors have been corrected.

[A bunch of stacktraces...]

12:30:39,057 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50030 VDB MyVDB.1 model "my_vdb" metadata loaded. End Time: 10/6/16 12:30 PM

12:30:39,062 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID40003 VDB MyVDB.1 is set to ACTIVE

So my question is: is there a way to make the VDB start up synchronously, so it can finish its deployment and only then the application starts? Or is there any other solution to this issue?

Thanks in advance,

Jorge

[shawkins]

> So my question is: is there a way to make the VDB start up synchronously, so it can finish its deployment and only then the application starts? Or is there any other solution to this issue?

The built-in support we provide is for local connections.  There is a waitForLoad parameter - jdbc:teiid:test.1;waitForLoad=5000  that specifies how long in milliseconds the connection should wait for the specified vdb (the version is required) to appear.

[jorgecmb]

Thanks Steven, but I am using TEIID 8.12.x and this parameter was deprecated in version 8.11: (source: Teiid ${project.version} Release Notes )

• TEIID-3576 the waitForLoad connection property has been deprecated.

Any other ideas?

[shawkins]

Sorry, the deprecation is to use the loginTimeout property instead:

jdbc:teiid:test.1;loginTimeout=5

[jorgecmb]

Thanks Steven, I will try adding the loginTimeout. As we were in a tight deadline, we decided to add a 2 minutes delay between the VDB and application deployment, which seems to have done the trick for now. Hope that the parameter is a permanent fix.

[shawkins]

I had to refresh myself on the resolution of that issue.  The most important thing is that the vdb version is specified.  For local connections with the vdb version the default timeout for the vdb to load is 5 minutes - System Properties · Teiid Documentation the clientVdbLoadTimeoutMillis property.  Setting the loginTtimeout in the URL will then supersede that value.