Description
When deploying Strategy Web Services Universal J2EE the JAVA process listens not only to the default HTTP TCP port (e.g. 8080) but also to additional ports in the 606x range (TCP 6061 - TCP 6064). The Web Server configuration files do not declare any of these additional ports.
The following is the output of a netstat command on Linux before and after deploying Strategy Web Services on Tomcat 6.0:
Before Deployment
Sample Code/Error
tcp 0 0 :::8009 :::* LISTEN 13778/java
tcp 0 0 :::8080 :::* LISTEN 13778/java
After Deployment
Sample Code/Error
tcp 0 0 :::8009 :::* LISTEN 13778/java
tcp 0 0 :::6061 :::* LISTEN 13778/java
tcp 0 0 :::6062 :::* LISTEN 13778/java
tcp 0 0 :::8080 :::* LISTEN 13778/java
Cause
Strategy Web Services 9.x incorporates parts of Apache Axis 1.2 to provide Java Web Services functionality. By default Axis listens on TCP port 8080 but it falls back to TCP port 6061 if port 8080 is occupied. In this scenario, Strategy Web Services listens on port 8080 which then requires Apache Axis to listen of ports listed above.
Note that port 6061 is not required by Strategy Web Services to function properly. An Enhancement Request has been logged to avoid Strategy Web Services deployments to listen on ports other than the default port (8080 or as per Web Server configuration). For general information about ports used by Strategy 9.x Product suite, refer to KB34971: What TCP/IP ports are used by the MicroStrategy 9.x Product Suite.
Action
Please contact Strategy Technical Support for an update on this issue.
