• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

RMI Callback using socket pools

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have an application with client and server making numerous RMI callbacks as events occur and are posted to the server.

The client registers with the server to be notified when these events occur, and the server can invoke remote methods on the client.

The client and server are seperated by a firewall which is blocking the callback mechanism - this is a new infrastructure deployment within the last 30 days.

What I would like to try is to have a customized socket factory that is invoked when an event occurs that will create a socket with a specific TCP port. Since there are multiple events that are being posted from the server to the client (upwards to 100 per client/server interactions depending on the information context) I would also like a method to close a given port after the callback mechanism has completed and close that socket returning it to the available pool.

Has anybody done this type of distributed communications programming?
 
Bartender
Posts: 4121
IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think there's an example of creating a special RMISocketFactory for HTTP tunnelling in the O'Reilly "Java RMI" book...

There's a tutorial on Sun's website about How to use custom socket factories in RMI.

You could easily make the socket factory pull the socket from a pool, but I don't think there is a way for the socket factory itself to know when it is time to put the socket back in the pool... only the client using the socket will know when it is done and it is time to put the socket back (I suppose you could wrap this somehow with another class that the client uses that has a reference to the same socket pool.), and there may be problems with sockets timing out and not being returned to the pool...

Sorry I couldn't help you more, but hopefully this gives you some information that can help you out.
 
Bruce Rosenthal
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Nathan.

HTTP tunneling will not work here because the events that the server-side are posting back to client GUI are each running in their own thread.

That's why I need the pool of sockets which I will have the firewall opened for.

Here is what I have come up with so far if you would like to look at it and give me your initial feed-back:

public class FixedPortRMISocketFactory extends RMISocketFactory {

public static Integer pv;
public static int clPort = 6051;
public static int svPort = 6000;
/**
* Creates a client socket connected to the specified host and port and writes out debugging info
* @param host the host name
* @param port the port number
* @return a socket connected to the specified host and port.
* @exception IOException if an I/O error occurs during socket creation
*/
public Socket createSocket(String host, int port)
throws IOException {

InetAddress ip = InetAddress.getLocalHost();
synchronized (this) {

//return new Socket(host, port);
System.out.println (" Thread : " + Thread.currentThread());
try {
Socket clSock = new Socket(host, port, ip, clPort);
System.out.println("created client socket to host : " + host + " on serverport " + port + " localip " + ip.getHostAddress() + " localPort " + clPort);
return clSock;
}
catch (Exception e){
System.out.println("Cannot create Client socket at port " + clPort + " : " + e.toString());
throw new IOException();
}
}
}

/**
* Create a server socket on the specified port (port 0 indicates
* an anonymous port) and writes out some debugging info
* @param port the port number
* @return the server socket pool for array access of sockets by the event thread caller
* @exception IOException if an I/O error occurs during server socket
* creation
*/
public ServerSocket createServerSocket(int port)
throws IOException {
port = (port == 0 ? svPort : port);
ServerSocket svSockPool[] = new ServerSocket[50];

for ( sockID = port; sockID < 6051 ; sockID++ )
{

ServerSocket svSock;

try {
svSockPool[sockID] = new ServerSocket(sockID);
svSock = svSockPool[sockID];
System.out.println("created ServerSocket on serverport " + sockID);
svPort ++ ;
if(svPort == 6050)
svPort = 6000;
/* svPort pool at end of range so reset to 6000 */

}
catch (Exception e){
System.out.println("Cannot create Server socket at port " + port + ": " + e.toString());
throw new IOException();
}
return (ServerSocket)svSockPool[];
}
}
}
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic