I'm a contractor working for a large telecom company which has a legacy system into which has been introduced a twist, and I'd like to describe the general setup, as it appears JBoss Remoting Multiplex may offer a solution.
A client app connects to a server using a proprietary messaging protocol based on Java TCP sockets. The client, using a standard Java Socket, sends a message to the server on its "well known" port, telling the server (in the message) to reply to it on the standard dynamic remote port (generally in the range 49152 to 65535). In this legacy app, the client listens asynchronously for messages with a standard ServerSocket on the dynamic port. Client & server are appropriately threaded supporting multiple sessions. So far so much.
The twist/wrinkle is, as you can guess, a firewall is now required between the client and server, so the use of dynamic ports is out. Rather than muck with the low-level details of the legacy code, one solution might be to use JBoss Remoting Multiplex classes in an intermediate process between client and server, using a single static reply socket.
My question is simply: does this seem like an approach we should pursue? I am at the moment a JBoss newbie, hence the question. Any replies appreciated, thanks.