https socket-binding exists but no https connector

Solution Verified - Updated -

Environment

  • JBoss Enterprise Application Platform (EAP) 6

Issue

  • We see a https socket binding defined in our JBoss xml config, but there's no https connector using it in the web subsystem. Why is this?

Resolution

  • The https connector is not defined by default. The socket bindings for http, https an ajp are all defined by default though, indicating the typical defaut ports for these connectors. The socket binding is only effectively used though if referenced by a connector in the web subsystem. Default non-ha profiles only ship with the http connector enabled by default and ha profiles ship with the http and ajp connector by default, but all of them would have the http, https, and ajp socket-binding provided by default.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.