axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjiva Weerawarana <sanj...@opensource.lk>
Subject Re: [jira] Created: (AXIS2-2834) When the client's preferred HTTP listener port is taken, find another one that isn't
Date Thu, 21 Jun 2007 15:58:36 GMT
+1 .. would be great to fix this for 1.3.

Sanjiva.

Paul Fremantle (JIRA) wrote:
> 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: Axis 2.0 (Axis2)
>           Issue Type: Improvement
>     Affects Versions: 1.2
>             Reporter: Paul Fremantle
>              Fix For: 1.3
> 
> 
> 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 .
> 

-- 
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message