[
https://issues.jboss.org/browse/TEIID-5526?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5526:
---------------------------------------
If you define a vdb and there is a source for which a jndi name is
not matched with a data source from the configuration, the vdb will still be deployed, but
won't be active
To clarify, this is only for the case where the source metadata is not provided and cannot
be obtained without a connection. If the jndi name does not match and we have metadata
the vdb will deploy and be active.
and there is no indication in the default console log as to the
progress or lack thereof with the metadata load.
There is always the log about metadata load starting. And testing this some more I do
see appropriate failure logs.
Given the presumed static nature of thorntail deployments, this
scenario should result in a failed deployment like embedded.
It seems like this would either need to be a build time validation or something that can
be detected via running/health check. Our initial versions of those would only detect
this when the metadata is not available.
Given that I'm seeing appropriate error messages, I'll not worry about this yet.
> Missing data source thorntail
> -----------------------------
>
> Key: TEIID-5526
> URL:
https://issues.jboss.org/browse/TEIID-5526
> Project: Teiid
> Issue Type: Quality Risk
> Components: thorntail
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.x
>
>
> If you define a vdb and there is a source for which a jndi name is not matched with a
data source from the configuration, the vdb will still be deployed, but won't be
active - and there is no indication in the default console log as to the progress or lack
thereof with the metadata load.
Given the presumed static nature of thorntail deployments, this
scenario should result in a failed deployment like embedded.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)