1) Start openfire
2) Check httpbind settings, https port is 0
3) set it to some other port, https httpbind starts up
4) shut down openfire
5) start up openfire, httpbind is not running
will investigate more.
I think I figured out the bug, but I may be off the base.
the sslEnabled variable only has the chance to be set true when configureHttpBindServer is called. Otherwise, it will always be false and thus getHttpBindSecurePort will always return 0 , which will cause start() to fail, since configureHttpBindServer is called after getHttpBindSecurePort()
Will think some more about a patch for this.
Bug appears to be introduced with this changeset.
I am not sure what Clearspace needs for a port number return when https bind is disabled and if reverting parts of this patch break what CS wants. sorry