Hey guys.
I am trying to establish two Socket connections between to applications, over a network (well, I'm currently testing just on my local machine).
On the Server-application, I'm doing this:
Socket sock1; // Class instance
Socket sock2; //
...
ServerSocket srv = new ServerSocket( port );
sock1 = srv.accept();
try
{
ServerSocket srv2 = new ServerSocket( port );
srv2.setSoTimeout( 10 *1000 );
sock2 = srv2.accept();
} catch ( InterruptedIOException ioe2 )
{
error( "Timeout exception occured." );
} catch ( Exception e2 )
{
e2.printStackTrace();
}
Then on the client-application:
Socket sock1; // Class Instance
Socket sock2; //
...
sock1 = new Socket( InetAddress.getByName( server ), port );
sock2 = new Socket( InetAddress.getByName( server ), port );
Obviously, it's all in try{}catch statements appropriately.. Now, when I run it, what appear to be happening, is that the first connection is made without problem, but then a problem occurs on the second connection attempt.. The server is throwing the following exception:
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.s
at java.net.PlainSocketImpl.b
at java.net.ServerSocket.bind
at java.net.ServerSocket.<ini
at java.net.ServerSocket.<ini
at ConnHandler.run(ConnHandle
Where ConnHandler.java is the Server class, and line 48 is this line:
ServerSocket srv2 = new ServerSocket( port );
Why is it not making a second connection? What would you say is the best way to achieve this?
Regards;
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
When a ServerSocket object is created, it attempts to bind to the port on the local host given by the port argument.
If another server socket is already listening to the port, then a java.net.BindException, a subclass of IOException, is thrown.
No more than one process or thread can listen to a particular port at a time. This includes non-Java processes or threads.
For example, if there's already an HTTP server running on port 80, you won't be able to bind to port 80.
-CE
But, from my first attempt, what it *should* do (at least, what I would expect it to do), is listen on the 'port', then block until it accepts a connection, with this command:
sock1 = srv.accept();
Then, that should stop it from listenning on that port... right? And then, I can create a new ServerSocket on that same port..?
Or, do I need to do something like this:
ServerSocket srv1 = new ServerSocket( port );
sock1 = srv1.accept();
srv1.close();
ServerSocket srv2 = new ServerSocket( port );
sock2 = srv2.accept();
srv2.close();
??
If you're only wanting the server to accept connections through one port, you only need one ServerSocket object. However, you need to spawn a new thread each time the ServerSocket's accept() method returns.
<pseudocode alert!>
ServerSocket svr = new ServerSocket( port );
Socket s = srv1.accept();
while( some_condition )
{
MySocketThread t = new MySocketThread(s);
t.start();
s = srv1.accept();
}
<and elsewhere in the server>
public class MySocketThread extends Thread
{
private Socket s;
public MySocketThread(Socket sock)
{
s = sock;
}
public void run()
{
//do your server-side stuff here
}
}
Business Accounts
Answer for Membership
by: InteractiveMindPosted on 2005-04-08 at 04:16:12ID: 13734916
do I need to do:
srv.close();
before creating the second ServerSocket? I haven't bothered trying it; because I'm guessing that it would close sock1, right?