Menu Search

7.4. VirtualHosts

A virtualhost is a independent namespace in which messaging is performed. Virtualhosts are responsible for the storage of message data.

Virtualhosts can only be managed by the HTTP management channel.

7.4.1. Types

The following virtualhost types are supported.

  • BDB - Virtualhost backed with Oracle Berkeley DB JE

  • BDB HA - Virtualhost backed with Oracle BDB utilising High Availability

  • DERBY - Virtualhost backed with Apache Derby

  • JDBC - Virtualhost backed with an external database [6]

  • Memory - In-memory node (changes lost on Broker restart)

  • Provided - Virtualhost that co-locates message data within the parent virtualhost node [7].

7.4.2. Context

7.4.3. Attributes

  • Name the virtualhost. This is the name the messaging clients refer to when forming a connection to the Broker.

  • Store Path/JDBC URL. Refers the file system location or database URL used to store the message data.

  • Store overflow/underflow. Some virtualhosts have the ability to limit the of the cumulative size of all the messages contained within the store. This feature is described in detail Section 9.2, “Disk Space Management”.

  • Connection thread pool size. Number of worker threads used to perform messaging with connected clients.

    Defaults to 64 or double the maximum number of available processors, whichever is the larger.

  • Number of selectors. Number of worker threads used from the thread pool to dispatch I/O activity to the worker threads.

    Defaults to one eighth of the thread pool size. Minimum 1.

  • Store transaction timeouts. Warns of long running producer transactions. See Section 9.3, “Transaction Timeout”

  • Synchronization policy. HA only. See Section 10.4.2, “Synchronization Policy”

7.4.4. Children

7.4.5. Lifecycle

  • Stop. Stops the virtualhost. This closes any existing messaging connections to the virtualhost and prevents new ones. Any inflight transactions are rolled back. Non durable queues and non durable exchanges are lost. Transient messages or persistent messages on non-durable queues are lost.

  • Start. Activates the virtualhost.

[6] JDBC 4.0 compatible drivers must be available. See Section F.2, “Installing External JDBC Driver”

[7] Not available if Virtualhost Node type is JSON.