This processor is deprecated and may be removed in future releases.
Please consider using one the following alternatives: ConsumeJMS
Pulls messages from a ActiveMQ JMS Topic, creating a FlowFile for each JMS Message or bundle of messages, as configured.
jms, topic, subscription, durable, non-durable, listen, get, pull, source, consume, consumer
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.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| JMS Provider | JMS Provider | ActiveMQ |
| The Provider used for the JMS Server |
| URL | URL | The URL of the JMS Server | ||
| Destination Name | Destination Name | The name of the JMS Topic or queue to use | ||
| Communications Timeout | 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 | Message Batch Size | 10 | The number of messages to pull/push in a single iteration of the processor | |
| Username | Username | Username used for authentication and authorization | ||
| Password | Password | Password used for authentication and authorization Sensitive Property: true | ||
| SSL Context Service | SSL Context Service | Controller Service API: SSLContextService Implementations: StandardRestrictedSSLContextService StandardSSLContextService | The Controller Service to use in order to obtain an SSL Context. | |
| Acknowledgement Mode | Acknowledgement Mode | Client 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 Selector | Message Selector | The JMS Message Selector to use in order to narrow the messages that are pulled | ||
| Copy JMS Properties to Attributes | Copy JMS Properties to Attributes | true |
| 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 Prefix | 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 | ||
| Use Durable Subscription | Use Durable Subscription | false |
| If true, connections to the specified topic will use Durable Subscription so that messages are queued when we are not pulling them |
| Name | Description |
|---|---|
| success | All FlowFiles are routed to success |