Supporting of different configurations for different requests is broken for
AxisServlet.
----------------------------------------------------------------------------------------
Key: AXIS2-4519
URL: https://issues.apache.org/jira/browse/AXIS2-4519
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel, transports
Affects Versions: nightly
Environment: FreeBSD 6.2, Apache 2.22, Diablo JDK 1.5, Tomcat 6.0.14
Reporter: Maslakov Denis
AxisServlet does not support different configurations for different requests
for one instance of Axis2 web-services under Tomcat.
The configuration of web-services is:
1. The frontend is Apache web-server on 80 port.
The Apache contains virtual domain (webservices.domain.ru) for redirecting
request to Tomcat (through mod_jk).
The request for web-service is
http://webservices.domain.ru/context-path1/services/WSService/
2. The backend of web-services is Axis2 under Tomcat on 8180 port.
The request for web-service is http://<ip>:8180/axis2-test/services/WSService/
Here axis2-test is name of webapp Axis2 and so context path.
The external users inquire web-service from Apache.
The internal users inquire same web-services directly from Tomcat.
Nevertheless, class AxisServletListener will catch port from the first request
of user. If it will be request from external user, then port will be 80 for all
users. If it will be request from internal user, then port will be 8180 for all
users.
The context path from request also will be different.
It happens as AxisServlet instance contains only one listener and one path of
context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
