I'm adding this to the end of Chapter 6. If anyone wants to review it:
6.5. Configuring the remoting connector
JBoss Messaging uses JBoss Remoting for all client to server communication. For
full details of what JBoss Remoting is capable of and how it is configured
please consult the JBoss Remoting documentation.
The default configuration includes a single remoting connector which is used by
the single default connection factory. Each connection factory can be
configured to use its own connector.
The default connector is configured to use the remoting socket transport.
This transport opens TCP connections from client to server for client to server
communications (e.g. sending messages) and TCP connections from server to
client for server to client communications (e.g. receiving messages). The
transport can be configured to use SSL where a higher level of security is
required.
Future releases JBoss Messaging will support a bidirectional socket transport
(similar to UIL2 in JBoss MQ) and an HTTP transport, both of which are useful
in network environments where TCP connections from server to client are not
possible. This means, for example, that you could deploy one connection factory
that uses the HTTP transport for all the connections created from it, and
another connection factory that uses the socket transport for all connections
created from it.
You can look at remoting configuration under:
/server//deploy/jboss-messaging.sar/remoting-service.xml
By default JBoss Messaging binds to ${jboss.bind.address} which can be defined
by: ./run.sh -c -b yourIP.
You can change remoting-service.xml if you want for example use a different
communication port, or any other network behavior.
6.6. Configuring the callback
JBoss Messaging uses a callback mechanism from Remoting that needs a Socket for
callback operations. These socket properties are passed to the server by a
remote call when the connection is being estabilished. As we said before we
will support bidirectional protocols in future releases.
By default JBoss Messaging will execute
InetAddress.getLocalHost().getHostAddress() to access your local host IP, but
in case you need to setup a different IP, you can define a system property in
your java arguments:
Use java -Djboss.messaging.callback.bind.address=YourHost - That will determine
the callBack host in your client.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973103#3973103
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973103
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
