You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Wayne Johnson (JIRA)" <ax...@ws.apache.org> on 2007/06/25 19:14:25 UTC
[jira] Commented: (AXIS-1708) log port open failures in SOAPMonitor
[ https://issues.apache.org/jira/browse/AXIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507927 ]
Wayne Johnson commented on AXIS-1708:
-------------------------------------
I spent all morning trying to track down the fact that port 5001 was already in use. Given the number of postings with "soap monitor is unable to communicate" and no responses, I would really like to see this be made higher priority. At least change the html generation code in SOAPMonitorService.java to send an error message rather than load the applet with a port=0. Can't be more that 10 lines of code.
> log port open failures in SOAPMonitor
> -------------------------------------
>
> Key: AXIS-1708
> URL: https://issues.apache.org/jira/browse/AXIS-1708
> Project: Axis
> Issue Type: Improvement
> Affects Versions: 1.2RC2
> Environment: fedora core 2
> axis cvs as of 2004-12-08
> Reporter: toby cabot
> Priority: Minor
> Attachments: axis-log-port-failure-patch.txt
>
>
> When the SOAPMonitor service can't open the port that's specified in web.xml it doesn't log anything, and it tells the applet to connect on port 0. It should log the problem and send an error to people who try to download the servlet. I'll attach a patch that makes these changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org