Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.6.1
-
Fix Version/s: 3.6.2
-
Component/s: None
-
Acceptance Test - Add?:No
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 3.6.2 [ 10832 ] |
| 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 https is not running will investigate more. |
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. |
| Summary | Something prevents https httpbind from starting up in some cases | sslEnable in HttpBindManager always false at boot, causing httpbind not to start |
| Summary | sslEnable in HttpBindManager always false at boot, causing httpbind not to start | sslEnabled in HttpBindManager always false at boot, causing httpbind not to start |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
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