[ https://issues.apache.org/jira/browse/AXIS2-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Muthuvelan Swaminathan updated AXIS2-4472: ------------------------------------------ Attachment: web.xml SOAPMonitorConstants.java SOAPMonitorService.java Create server socket using IPaddress and Port if IPaddress is configured as part of init-param for the servlet. Here is the modified web.xml which passes the ip address as an init-param <!-- SoapMonitor --> <servlet> <servlet-name>SOAPMonitorService</servlet-name> <display-name>SOAPMonitorService</display-name> <servlet-class>org.apache.axis2.soapmonitor.servlet.SOAPMonitorService</servlet-class> <init-param> <param-name>SOAPMonitorHostIP</param-name> <param-value>10.2.154.115</param-value> </init-param> <init-param> <param-name>SOAPMonitorPort</param-name> <param-value>5001</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>SOAPMonitorService</servlet-name> <url-pattern>/SOAPMonitor</url-pattern> </servlet-mapping> Support for init-param "SOAPMonitorHostIP" is added to SOAPMonitoConstants and SOAPMonitorService > Running soap-monitor in a machine with multiple catalina_base with its own ip > address > ------------------------------------------------------------------------------------- > > Key: AXIS2-4472 > URL: https://issues.apache.org/jira/browse/AXIS2-4472 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: Tools > Environment: Windows / Linux > Reporter: Muthuvelan Swaminathan > Attachments: SOAPMonitorConstants.java, SOAPMonitorService.java, > web.xml > > Original Estimate: 4h > Remaining Estimate: 4h > > In environment where we run multiple tomcat instances using CATALINA_BASE and > if each instance is bounded to its own ip address running soapmonitor results > in an error as the socket connection uses localhost when creating the server > socket. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.