activemq--Configuration Port

Configure Ports Port configuration Options

The most commonly used URI is the port URI that is connected to the proxy, usually the TCP or VM port.

Note the spaces: All URIs are based on the Java.net.URI class, and it does not allow spaces to be used. So, if you use failover: or Static:uri, don't leave a blank in the comma.

Virtual Machine Port

Virtual machine ports allow customers to connect to each other within a virtual machine without using the network connections on them. This connection is not a socket connection, but is used directly to increase the performance of the embedded messaging system.

The first client using the virtual machine will be used to boot an embedded agent, and then the connection will be attached to the same agent. The embedded agent will also be closed once the virtual machine used to connect to the agent is turned off.

For more information, refer to the virtual machine port reference. TCP Port

The TCP port allows a client to connect to a remote ACTIVEMQ using a TCP socket.

For more information, refer to the TCP port reference. NiO Port

This may provide better performance, except for the remaining TCP ports that use the new I/O package. Note that the Java NIO package does not cause conflicts with IBM's AIO4J package.

Switching from TCP to NIO requires a simple change to the URI configuration scenario, and the following is an XML configuration file that defines NIO.

<broker>

...

<transportConnectors>

<transportconnector name= "NiO" uri= "nio://0.0.0.0:61616"/>

</<transportConnectors>

...

</broker>

SSL Port

Allows you to use SSL via TCP (encrypted via network channel information).

For more information, check the SSL port reference. NIO SSL Ports

SSL transmission is achieved through NIO. This allows you to use a proxy instance to connect a large number of SSL clients. This is just the server-side port option.

<broker>

...

<transportConnectors>

<transportconnector name= "Nio+ssl" uri= "nio+ssl://0.0.0.0:61616"/>

</<transportConnectors>

...

</broker>

Using the Nio+ssl port URL on the client initializes the regular SSL port. Peer Network Port

This port provides an end-to-end network of users using ACTIVEMQ. It actually uses the virtual machine port to establish a local proxy connection, and the local agent establishes the network configuration to connect to the other end of the embedded agent.

For more information, refer to the peer network port reference. UDP port

Allows you to talk through UDP.

For more information, see the UIP port reference. Multicast Port

Allows you to talk through multicast.

For more information, see the multicast port reference. http and HTTPS ports

Allows ACTIVEMQ clients and agents to establish channels through HTTP. If the customer is not JMS, you may want to know about rest or Ajax support.

For more information, check the HTTP and HTTPS port references. WebSockets Port

This port uses Html5websockets to interact with agent information. For more information, refer to the WebSockets port reference. Universal URI

You can use URI syntax for some configuration of other features. Connection Configuration URI

Any activemq JMS connection can be configured using a URL or set properties directly in Activemqconnectionfactory or Activemqconnection objects. Target Options

You can use the URI syntax to configure different target options. Agent configuration Uri

You can configure the embedded proxy using the proxy configuration URI, or you can use the Brokerfactory helper in Java code, or use the ACTIVEMQ shell script. For more information, see How to run the agent. Configure wire Format

The Openwire format is recommended for transferring marshalling messages over a network port, which is also configurable.

For more information, see Configuring the Wire format.

Advanced Protocol URI

A more advanced protocol can be configured through a URI. Failover Ports

The failover port layer has a new connection priority for the other ports. This was once used for ACTIVEMQ 3. Its configuration syntax allows you to specify a number of compound URIs. The failover port randomly selects a composite URI to attempt to establish a connection. If it is unsuccessful, select one from the list of URIs to create a new connection.

For more information, refer to the failover port reference. Fan out Port

The fan-out port layer is reconnected to the top of the other ports and copies the logic. It is used to copy commands into multiple agents.

For more information, see Fan out port reference. Use Discovery

Typically, you want to locate and locate a valid proxy when using the TCP port. It's different in terms of usage, parlance, and multicast. Using TCP as the primary means of communication rather than multicast, the discovery function is purely for discovering the location of the agent. Discovery Port

The discovery Port works like a trusted port, except that it uses a discovery agent to locate the list of URIs to connect to.

See the discovery Port reference for more information. 0 Configuration Port

The 0 configuration port can provide discovery and work like a discovery port, but it is based on the discovery mechanism using its own multicast (which allows you to configure an exact multicast address and port),

For more information, check the 0 configuration port reference. server-side options

There are a number of options that are used to change server-side behavior.

Property name	Default Value	Description
Uri	Null	and ports to bind
Name	Null	Port Connection Instance Name
Discoveryuri	Null	If set, the client-connected multicast discovery address is used to discover the agent.
Enablestatusmonitor	False	Monitor the connection to determine whether to block.
Updateclusterclients	False	Enable the client connection that will update the change agent group
Rebalanceclusterclients	False	Automatically new balancing of clients through group topology changes.
Updateclusterclientsonremove	False	If the agent is removed from the cluster, the agent will be updated.
Updateclusterfilter	Null	Comma-delimited regular expression, and the agent for the name matching template will be updated by the customer.

Note: The red attribute is only valid for version 5.4.

Configuration Example:

<broker>

...

<transportConnectors>

<transportconnector name= "Openwire" uri= "tcp://0.0.0.0:61616" enablestatusmonitor= "true"/>

</<transportConnectors>

...

</broker>