Creates a JMS Message from the contents of a FlowFile and sends the message to a JMS Server


jms, send, put


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the Expression Language Guide, and whether a property is considered “sensitive”, meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the file has an entry for the property nifi.sensitive.props.key.

Name Default Value Allowable Values Description
JMS Provider ActiveMQ * ActiveMQ The Provider used for the JMS Server
URL The URL of the JMS Server
Destination Name The name of the JMS Topic or queue to use
Destination Type Queue * Queue
* Topic
The type of the JMS Destination to use
Communications Timeout 30 sec The amount of time to wait when attempting to receive a message before giving up and assuming failure
Message Batch Size 10 The number of messages to pull/push in a single iteration of the processor
Username Username used for authentication and authorization
Password Password used for authentication and authorization
Sensitive Property: true
SSL Context Service Controller Service API:
The Controller Service to use in order to obtain an SSL Context.
Message Type byte * byte
* stream
* text
* map
* empty
The Type of JMS Message to Construct
Message Priority The Priority of the Message
Supports Expression Language: true
Reply-To Queue The name of the queue to which a reply to should be added
Supports Expression Language: true
Max Buffer Size 1 MB The maximum amount of data that can be buffered for a JMS Message. If a FlowFile's size exceeds this value, the FlowFile will be routed to failure.
Message Time to Live The amount of time that the message should live on the destination before being removed; if not specified, the message will never expire.
Copy Attributes to JMS Properties true * true
* false
Whether or not FlowFile Attributes should be translated into JMS Message Properties. If true, all attributes starting with 'jms.' will be set as Properties on the JMS Message (without the 'jms.' prefix). If an attribute exists that starts with the same value but ends in '.type', that attribute will be used to determine the JMS Message Property type.
Client ID Prefix A human-readable ID that can be used to associate connections with yourself so that the maintainers of the JMS Server know who to contact if problems arise


Name Description
failure All FlowFiles that cannot be routed to the JMS destination are routed to this relationship
success All FlowFiles that are sent to the JMS destination are routed to this relationship

Reads Attributes:

None specified.

Writes Attributes:

None specified.

See Also:

GetJMSQueue, GetJMSTopic