[
https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on TEIID-2650:
-----------------------------------------
When you call
{code}
/profile=ha/subsystem=teiid:read-resource
{code}
you are asking the Host Controller you connected to for information about the *domain
wide* configuration. The Host Controller could fill in information for runtime-version
that is correct for it's own process, but it cannot provide information that's
correct domain wide. There is no such thing as a domain wide runtime-version because it is
perfectly legal to run multiple different versions on different hosts in a domain. It
isn't required, or even expected in large domains, for all hosts to be on the same
version. For example, different server groups might be running different applications, and
if the behavior of some of those apps is acceptable domain managers may choose not to
upgrade the hosts for those server groups when a new release comes out. Organizations are
often quite conservative in this regard.
A jboss server in domain mode does not advertise its teiid
runtime-version
--------------------------------------------------------------------------
Key: TEIID-2650
URL:
https://issues.jboss.org/browse/TEIID-2650
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.4
Reporter: Paul Richardson
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 8.4.1, 8.5
A standalone jboss server installed with teiid advertises its teiid runtime version at
the path /subsystem=teiid/runtime-version.
Likewise, a domain jboss server installed with teiid in the 'ha' profile should
advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version.
However, whereas the standalone returns the correct value for this attribute, the domain
mode server fails, only returning 'undefined'.
This attribute is essential to designer in determining what version is the teiid
instance. This in turns determines the functionality of the modelling that is available
and which teiid client should be used for connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira