In the directory org.jboss.remoting.samples.multiplex are examples of virtual socket use. In the directory org.jboss.remoting.samples.multiplex.invoker are examples of use of the multiplex transport.
That said, I'm encouraging people to consider the bisocket transport in place of multiplex. They were both designed to support clients behind firewalls, but bisocket is faster and probably more reliable. It is used by JBossMessaging, which means it gets a lot of production use. I'm not aware of any comparable use of the multiplex transport.
I just noticed that you mentioned SSl in the thread title. There is a version of multiplex called sslmultiplex. I don't see any sslmultiplex sample code, but there is a lot of unit test code in org.jboss.test.remoting.transport.multiplex.ssl and subpackages.
Again, consider sslbisocket.
Thank you very much.
I'll start migrating my code to bisocket.
Good choice. It's a new transport, and we're still working out some wrinkles, so keep an eye out for updated releases at http://repository.jboss.com/jboss/remoting/. The most recent jboss-remoting.jar there is in the 2.2.0.SP4_CP02-brew/ directory, though it's not an official release. It should be superseded soon by an evolution of 2.2.1.GA, which will probably be called 2.2.1.SP1.