ACTIVEMQ Pure Static routing configuration

      ACTIVEMQ Pure static routing configuration, used to transparently transfer messages between two servers. For example, there are two servers A and B, and we create a new message queue on Server A to transfer to the B server. This allows us to adopt a purely static routing configuration. This mode, a server's message directly to B server, a server production message, directly on the spot to the B server, while the B server received a server message (relative a server is a producer) to wait until the B server on the consumption of people over.        First install message Server A and B, note that the configuration port is inconsistent with a server port in the Activemq.xml configuration file of Server B. For example, a server port is 61616, then the B server can be configured to 61617. Similarly, the jetty.xml also needs to configure the Web server's port address and the a server do not conflict.        Configure the Activemq.xml file for a server, set up a pure static route, note that this configuration needs to be written in the persistent configuration <persistenceAdapter> before. <networkConnectors> <networkconnector uri= "static: (tcp://localhost:61617)" staticbridge= "true" >         <staticallyIncludedDestinations>                 <qu Eue physicalname= ">"/>         </staticallyIncludedDestinations> </ networkconnector> </networkConnectors>        above code stating that the delivery address is a B server (port 61617), Note that the Staticbridge parameter here sets a static route. Staticallyincludeddestinations a queue or broadcast that is also to be passed. Here the <queue physicalname= is used.> "/> is all queue messages. If written as <queue physicalname= "Foo,bar"/> Only the above two messages are synchronized. The following transmission queue message to a server, visible a server directly transparent delivery message (consumption)
b The server receives the message and waits for consumption.