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 "Paul Fremantle (JIRA)" <ji...@apache.org> on 2007/06/21 14:47:25 UTC
[jira] Created: (AXIS2-2834) When the client's preferred HTTP
listener port is taken, find another one that isn't
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 .
--
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
Re: [jira] Created: (AXIS2-2834) When the client's preferred HTTP
listener port is taken, find another one that isn't
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+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
[jira] Updated: (AXIS2-2834) When the client's preferred HTTP
listener port is taken, find another one that isn't
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2834:
------------------------------------
Assignee: Deepal Jayasinghe
> 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
> Assignee: Deepal Jayasinghe
> 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 .
--
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
[jira] Updated: (AXIS2-2834) When the client's preferred HTTP
listener port is taken, find another one that isn't
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2834:
------------------------------------
Fix Version/s: (was: 1.3)
> 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
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org