[
https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug...
]
Ramesh Reddy reopened TEIID-309:
--------------------------------
Assignee: Ramesh Reddy (was: Van Halbert)
More issues found during the system host setup they are
7) Host information put in for cluster member is not complete. When primary host is
created the host information is created using property replacement in the config.xml,
which accounts for all properties. However, during the admin api based host addition, it
will not add all the necessary information.
System Host setup issues
------------------------
Key: TEIID-309
URL:
https://jira.jboss.org/jira/browse/TEIID-309
Project: Teiid
Issue Type: Task
Components: Build/Kits
Affects Versions: 6.0.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.1.0
1) izpack does not make the startserver, stopserver, scripts as executable in the linux
2) There is no option for *not* starting the server (either way it does not look like
starting the server). This option should be extended to "setupmm" driven process
too, with additional property.
3) multicast port is not available in the IZpack + it is hard coded; Any two machines
are seeing each other on the same multicast address. This needs to be fixed as soon as
possible.(FEDERATE-340)
4) System name is always defaulting to $hostname, even when it is blank. I fixed this
in install.
5) With "systenhostsetup.sh" I can not pass in the properties file, it is
looking for the file in a fixed location.
6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not
write to the configuration about what it's config name is, thus never can be started.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira