We're updating the issue view to help you get more done. 

sslEnabled in HttpBindManager always false at boot, causing httpbind not to start

Description

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.

Environment

None

Acceptance Test - Entry

None

Activity

Show:
Daryl Herzmann
November 18, 2008, 1:12 PM

Hi,

I think I figured out the bug, but I may be off the base.

in HttpBindManager.java

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.

daryl

Daryl Herzmann
November 18, 2008, 1:22 PM

Bug appears to be introduced with this changeset.

http://www.igniterealtime.org/fisheye/changelog/svn-org?cs=10596

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

daryl

Assignee

Gaston Dombiak

Reporter

Daryl Herzmann

Labels

None

Expected Effort

None

Ignite Forum URL

None

Fix versions

Affects versions

Priority

Major
Configure