axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-725) "Address already in use: JVM_Bind" exception while creating second SimpleHTTPServer instance
Date Sun, 14 May 2006 03:08:18 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-725?page=comments#action_12394627 ] 

Sanjiva Weerawarana commented on AXIS2-725:
-------------------------------------------

You're absolutely right Jaliya .. and we have the capability thru ListenerManager (thru a
static config context approach; that's how we solve the problem for the servlet case). It
may be that we're not setting that for the SimpleAxisServer; so this is a bug which should
not require a workaround.

I mistakenly read the original issue as the user wanted to start two servers for some reason;
my bad.

In any case though, the code must loop thru to find an available port; its certainly possible
port 6060 is taken by someone else.

> "Address already in use: JVM_Bind" exception while creating second SimpleHTTPServer instance
> --------------------------------------------------------------------------------------------
>
>          Key: AXIS2-725
>          URL: http://issues.apache.org/jira/browse/AXIS2-725
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>     Versions: 1.0
>  Environment: Win2K Pro and WinXP Pro, JDK 1.4, Tomcat 5.5
>     Reporter: Ali Sadik Kumlali

>
> When I run two EchoNonBlockingDualClient sample at the same time, first one successfully
starts SimpleHTTPServer on port 6060 and the second one gets an java.net.BindException: Address
already in use: JVM_Bind" while trying to start the server.
> Doesn't I have an option to listen all the responses for its dedicated port? For example
6060 for the first instance, 6061 for the second one, and so on. Or, should i assume Axis2
to use the same port for the responses of all the long running transactions?
> Anyway, in either case, it should not throw such exception.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message