GetJMSTopic

Deprecation notice:

This processor is deprecated and may be removed in future releases.

Please consider using one the following alternatives: ConsumeJMS

Description:

Pulls messages from a ActiveMQ JMS Topic, creating a FlowFile for each JMS Message or bundle of messages, as configured.

Tags:

jms, topic, subscription, durable, non-durable, listen, get, pull, source, consume, consumer

Properties:

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, 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 nifi.properties file has an entry for the property nifi.sensitive.props.key.

NameDefault ValueAllowable ValuesDescription
JMS ProviderActiveMQ
  • ActiveMQ
The Provider used for the JMS Server
URLThe URL of the JMS Server
Destination NameThe name of the JMS Topic or queue to use
Communications Timeout30 secThe amount of time to wait when attempting to receive a message before giving up and assuming failure
Message Batch Size10The number of messages to pull/push in a single iteration of the processor
UsernameUsername used for authentication and authorization
PasswordPassword used for authentication and authorization
Sensitive Property: true
SSL Context ServiceController Service API:
SSLContextService
Implementation:StandardSSLContextService
The Controller Service to use in order to obtain an SSL Context.
Acknowledgement ModeClient Acknowledge
  • Client Acknowledge
  • Auto Acknowledge
The JMS Acknowledgement Mode. Using Auto Acknowledge can cause messages to be lost on restart of NiFi but may provide better performance than Client Acknowledge.
Message SelectorThe JMS Message Selector to use in order to narrow the messages that are pulled
Copy JMS Properties to Attributestrue
  • true
  • false
Whether or not the JMS Message Properties should be copied to the FlowFile Attributes; if so, the attribute name will be jms.XXX, where XXX is the JMS Property name
Client ID PrefixA 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
Use Durable Subscriptionfalse
  • true
  • false
If true, connections to the specified topic will use Durable Subscription so that messages are queued when we are not pulling them

Relationships:

NameDescription
successAll FlowFiles are routed to success

Reads Attributes:

None specified.

Writes Attributes:

None specified.

State management:

This component does not store state.

Restricted:

This component is not restricted.

Input requirement:

This component does not allow an incoming relationship.

See Also:

PutJMS