The message subsystem of wildfly evaluation

Wildfly, formerly JBoss as, from V8 to the difference from JBoss EAP, renamed to Wildfly. HORNETQ is an independent message-oriented middleware developed by JBoss and is integrated into wildfly as a message subsystem.

HORNETQ fully supports JMS,HORNETQ not only to support the JMS1.1 API but also to define its own messaging APIs (the core Client in the following figure) to maximize hornetq performance and flexibility.

Figure 1 Client program HORNETQ Two Interactive modes

For a description of the core client API, see: http://docs.jboss.org/hornetq/2.3.0.CR2/docs/api/hornetq-client/

1.1.1. Message type

HORNETQ is consistent with JMS to support two types of messages: point-to-point and publish/subscribe.

Point-to-Point

Figure 2 Point-to-Point of message types

Publish/subscribe

Figure 3 Publish/subscribe of message types

1.1.2. HORNETQ's Special terminology description

In order to better use the Wildfly message subsystem, it is necessary to give a description of its proprietary terminology. Two sets of concepts are more important:

Acceptors and Connectors

INVM and Netty

1.1.2.1. Acceptors and Connectors

Acceptor

Specify what type of connection HORNETQ server accepts (Connection)

Connector

Specify how HORNETQ server is connected to the client

The related configuration is defined in standalone and domain profile, and the following is a list of references.

<connectors>
    <netty-connector name= "Netty" socket-binding= "messaging"  />
    < Netty-connector name= "Netty-throughput" socket-binding= "Messaging-throughput" >
        <param key= "Batch-delay" Value= "/>"
    </netty-connector>
    <servlet-connector name= "servlet" socket-binding= "http" Host= "Default-host"  />
    <in-vm-connector name= "IN-VM" server-id= "0"  />
</connectors >
<acceptors>
    <netty-acceptor name= "Netty" socket-binding= "messaging"  />
    < Netty-acceptor name= "Netty-throughput" socket-binding= "Messaging-throughput" >
         <param key= "Batch-delay" Value= "/>"
        <param key= "Direct-deliver" value= "false"  />
    </netty-acceptor>
    <in-vm-acceptor name= "IN-VM" server-id= "0"  />
</acceptors>