[
https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin...
]
Paul Richardson commented on TEIID-2650:
----------------------------------------
Spent time creating queries through the domain master's client(?) servers and this
works well. Thanks for the info. However, I do not see why the teiid runtime version is
only available through these client servers. Since teiid is deployed onto the domain
master rather than its client servers, I don't understand why the runtime version is
not available in the location '/profile=ha/subsystem=teiid/runtime-version'.
I realise its not a static property and has no place in the config files yet it is filled
in correctly when the server is in standalone mode. It seems wrong that its
'undefined' for domain mode when we deploy teiid using the domain master. Maybe, I
am still misunderstanding domain mode?
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