-
1. Re: VDB is not active when war deploys
shawkins Oct 6, 2016 9:25 AM (in response to jorgecmb)> 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.
-
2. Re: VDB is not active when war deploys
jorgecmb Oct 6, 2016 9:39 AM (in response to shawkins)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?
-
3. Re: VDB is not active when war deploys
shawkins Oct 6, 2016 9:45 AM (in response to jorgecmb)Sorry, the deprecation is to use the loginTimeout property instead:
jdbc:teiid:test.1;loginTimeout=5
-
4. Re: VDB is not active when war deploys
jorgecmb Oct 6, 2016 11:37 AM (in response to shawkins)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.
-
5. Re: VDB is not active when war deploys
shawkins Oct 6, 2016 12:50 PM (in response to jorgecmb)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.