[
https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3666:
---------------------------------------
A VDB can be deployed before the datasources it depends on are fully
deployed and bound
That is expected.
resulting in the VDB never being marked as ACTIVE
That is not expected. The sequence of events shown in the ticket doesn't quite make
sense either as there are vdb reloads, but I didn't see what is triggering that.
In any case this may be expected behavior:
If data sources do not initially exist, since the vdb has dependencies on those services
it will wait to start until they are available.
If the data sources are available, but not usable due to stale connections, network
problems, etc., then the vdb service will attempt the start and fail. It will retry only
if the data source is removed and re-added or if an explicit Admin.markDataSourceAvailable
call is made to notify us that the data source is back up. We do not perform any polling
or retries.
VDB can deploy before datasource is bound
-----------------------------------------
Key: TEIID-3666
URL:
https://issues.jboss.org/browse/TEIID-3666
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.3
Environment: JDBC driver for datasource is deployed in deployments/ directory of
standalone instance
Reporter: Marc Shirley
Assignee: Steven Hawkins
A VDB can be deployed before the datasources it depends on are fully deployed and bound,
resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to
environments where the JDBC driver for the datasource is deployed through use of the
standalone deployments/ directory. If the driver is deployed as a module, then the risk
of the issue is lowered or eliminated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)