[ http://issues.apache.org/jira/browse/AXIS2-725?page=comments#action_12383383 ]
Jaliya Ekanayake commented on AXIS2-725: ---------------------------------------- I would like to suggest the approach where we use only one port per jvm. The reasons for not using many ports. We need to all of them across firewalls. It is so hard to debug by monitoring SOAP messages (using TCPMon or some other) We use the above approach in Sandesha1 and the last client simply closes the Listener. > "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
