Ondrej Zizka edited this page Jun 1, 2013 · 5 revisions


Migrates configuration of JBoss Remoting. The main objective of JBoss Remoting is to provide a single API for most network based invocations and related services that use pluggable transports and data marshallers.

Out of the box, Remoting supplies multiple transports (bisocket, http, rmi, socket, servlet, and their ssl enabled counterparts), standard and compressing data marshallers, and a configurable facility for switching between standard jdk serialization and JBoss Serialization. It is also capable of remote classloading, has extensive facilities for connection failure notification, performs call by reference optimization for client/server invocations collocated in a single JVM, and implements multihomed servers.

Files and characteristics

  • $JBOSS_HOME/server/$profile/deploy/messaging/remoting-bisocket-service.xml
  • $JBOSS_HOME/server/$profile/deploy/remoting-jboss-beans.xml
  • <mbean code="org.jboss.remoting.transport.Connector" .../>



Known issues / TODO's


Technical/logical limitations

  • The implementation is currently WARN-only.
  • Doesn't support multihomed servers.

References, documentation

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.