AxisServlet creates new listener for HTTPS port which blocks the containers
---------------------------------------------------------------------------
Key: AXIS2-4597
URL: https://issues.apache.org/jira/browse/AXIS2-4597
Project: Axis2
Issue Type: Bug
Components: transports
Affects Versions: 1.4, 1.4.1, 1.5, 1.6, 1.5.1
Environment: all
Reporter: Ben Reif
Priority: Critical
When you have an axis2.xml file that contains an https <transportReceiver> with
the application server's SSL port, you get a JVM_Bind exception on the https
port when you start some application servers such as Weblogic. This prevents
the application server from listening on that port and effectively disables
that port for all other applications running on that server. This is because
Weblogic doesn't try to bind to the http/https ports until after the
application has started, and if Axis2 has already been bound to that port then
Weblogic can no longer use it.
When the AxisServlet starts up the init(ServletConfig config) method registers
the TransportInDescription for the HTTP protocol with the ListenerManager as
"started", so it does not start a new listener for that port and Weblogic can
still bind to it. However it does not do that for HTTPS, which causes the
JVM_Bind exception. The AxisServlet should also register a
TransportInDescription for the HTTPS protocol as "started" in the
ListenerManager so that it does not block the container from binding to the SSL
port.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
