[
https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin...
]
Marc Shirley commented on TEIID-3666:
-------------------------------------
A sample log excerpt illustrating the issue is below. The metadata load is attempted but
fails due to the datasource still being in the process of deployment. In this case, the
datasource was fully deployed and bound 15 ms after the metadata load failed. The
metadata load is never reattempted and the VDB is never marked active in this scenario.
13:28:40,202 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB
DB2.1,608,121,347 model "TR" metadata failed to load. Reason:TEIID31097 Metadata
load requires a connection factory: TEIID30481 Failed to find the Connection Factory with
JNDI name TR. Please check the name or deploy the Connection Factory with specified name.
...
13:28:40,217 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-2) JBAS010400: Bound data source [java:/TR]
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)