axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ali Sadik Kumlali (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-725) "Address already in use: JVM_Bind" exception while creating second SimpleHTTPServer instance
Date Tue, 16 May 2006 20:06:07 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-725?page=comments#action_12412044 ] 

Ali Sadik Kumlali commented on AXIS2-725:
-----------------------------------------

Thanks Deepal. What I've got from your comments are:
- If I invoke the service from different JVMs, then JVM_Bind exception occurs because it loads
the port from the config file.
- Within the same JVM, if I invoke the service twice 
   - Without passing the same configuration context, then JVM_Bind exception occurs.
   - By passing the same configuration context, then no JVM_Bind exception occurs.

I did what you said and did not see JVM_Bind exception. But this time server sends an interesting
exception. You can find my test code, message flow (captured by sniffer), server log and client
log files attached. I think that is related to another issue AXIS2-741.


> "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
>     Assignee: Deepal Jayasinghe

>
> 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