axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2834) When the client's preferred HTTP listener port is taken, find another one that isn't
Date Sun, 19 Dec 2010 03:28:02 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Samisa Abeysinghe resolved AXIS2-2834.
--------------------------------------

    Resolution: Won't Fix

It has been too long that this has been open and with no action. If this is required, reopen
and fix. 

> When the client's preferred HTTP listener port is taken, find another one that isn't
> ------------------------------------------------------------------------------------
>
>                 Key: AXIS2-2834
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2834
>             Project: Axis2
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Paul Fremantle
>            Assignee: Deepal Jayasinghe
>
> When you run a client with setUseSeparateListener(true), it tries to open the port specified
in the axis2.xml. Quite often that port (8080) is already in use on the machine. Why don't
we have an option (enabled by default) to find another port and open on there. We do something
similar in Synapse. Since the client port is always specified in the replyTo header, it can
pretty much be anything and it doesn't matter, so I think this would be a nice option and
cause fewer Exception JVM_BIND address already in use .

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message