[
https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on TEIID-2650:
-----------------------------------------
Paul, you're not allowed to upgrade a host to a version later than the master. This is
because the master has to be able to understand all configuration options and intra-domain
communication protocols supported by any of the hosts. But, you are not required to
upgrade all hosts when you upgrade the master.
I do recommend that all servers in a server group be running on the same version, except
for during short windows during a rolling upgrade. That's general advice, not anything
specific to Teiid.
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