[#JM-1496] sslEnabled in HttpBindManager always false at boot, causing httpbind not to start

Openfire (ARCHIVED)

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

Created: 11/18/08 06:48 AM Updated: 11/20/08 10:12 AM

Component/s:

None

Affects Version/s:

3.6.1

Fix Version/s:

3.6.2

Time Tracking:

Not Specified

Support Plan Customer Issue:	No
Resolution Date:	11/20/08 10:12 AM
Acceptance Test - Add?:	No

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Daryl Herzmann added a comment - 11/18/08 07:12 AM

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

[ Permalink | « Hide ]

Daryl Herzmann added a comment - 11/18/08 07:22 AM

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