Skip to main content

ConsumeJMS

Description

Consumes JMS Message of type BytesMessage, TextMessage, ObjectMessage, MapMessage or StreamMessage transforming its content to a FlowFile and transitioning it to 'success' relationship. JMS attributes such as headers and properties will be copied as FlowFile attributes. MapMessages will be transformed into JSONs and then into byte arrays. The other types will have their raw contents as byte array transferred into the flowfile.

Tags

consume, get, jms, message, receive

Properties

In the list below required Properties are shown with an asterisk (*). Other properties are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Connection Factory ServiceConnection Factory ServiceController Service:
JMSConnectionFactoryProviderDefinition

Implementations:
JMSConnectionFactoryProvider
JndiJmsConnectionFactoryProvider
The Controller Service that is used to obtain Connection Factory. Alternatively, the 'JNDI *' or the 'JMS *' properties can also be be used to configure the Connection Factory.
Destination Name *Destination NameThe name of the JMS Destination. Usually provided by the administrator (e.g., 'topic://myTopic' or 'myTopic').

Supports Expression Language, using FlowFile attributes and Environment variables.
Destination Type *Destination TypeQUEUE
  • QUEUE
  • TOPIC
The type of the JMS Destination. Could be one of 'QUEUE' or 'TOPIC'. Usually provided by the administrator. Defaults to 'QUEUE'
Message SelectorMessage SelectorThe JMS Message Selector to filter the messages that the processor will receive

Supports Expression Language, using Environment variables.
User NameUser NameUser Name used for authentication and authorization.

Supports Expression Language, using Environment variables.
PasswordPasswordPassword used for authentication and authorization.
Connection Client IDConnection Client IDThe client id to be set on the connection, if set. For durable non shared consumer this is mandatory, for all others it is optional, typically with shared consumers it is undesirable to be set. Please see JMS spec for further details

Supports Expression Language, using Environment variables.
Character Set *character-setUTF-8The name of the character set to use to construct or interpret TextMessages

Supports Expression Language, using FlowFile attributes and Environment variables.
Acknowledgement Mode *Acknowledgement ModeCLIENT_ACKNOWLEDGE (2)
  • AUTO_ACKNOWLEDGE (1)
  • CLIENT_ACKNOWLEDGE (2)
  • DUPS_OK_ACKNOWLEDGE (3)
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.
Durable SubscriptionDurable subscriptionfalse
  • true
  • false
If destination is Topic if present then make it the consumer durable. @see https://jakarta.ee/specifications/platform/9/apidocs/jakarta/jms/session#createDurableConsumer-jakarta.jms.Topic-java.lang.String-

Supports Expression Language, using Environment variables.
Shared SubscriptionShared subscriptionfalse
  • true
  • false
If destination is Topic if present then make it the consumer shared. @see https://jakarta.ee/specifications/platform/9/apidocs/jakarta/jms/session#createSharedConsumer-jakarta.jms.Topic-java.lang.String-

Supports Expression Language, using Environment variables.
Subscription NameSubscription NameThe name of the subscription to use if destination is Topic and is shared or durable.

Supports Expression Language, using Environment variables.
Timeout *Timeout1 secHow long to wait to consume a message from the remote broker before giving up.

Supports Expression Language, using Environment variables.
Maximum Batch Size *Maximum Batch Size1The maximum number of messages to publish or consume in each invocation of the processor.
Error Queue NameError Queue NameThe name of a JMS Queue where - if set - unprocessed messages will be routed. Usually provided by the administrator (e.g., 'queue://myErrorQueue' or 'myErrorQueue').Only applicable if 'Destination Type' is set to 'QUEUE'

Supports Expression Language, using FlowFile attributes and Environment variables.
Record Readerrecord-readerController Service:
RecordReaderFactory

Implementations:
AvroReader
CEFReader
CSVReader
ExcelReader
GrokReader
JsonPathReader
JsonTreeReader
ReaderLookup
ScriptedReader
Syslog5424Reader
SyslogReader
WindowsEventLogReader
XMLReader
YamlTreeReader
The Record Reader to use for parsing received JMS Messages into Records.
Record Writer *record-writerController Service:
RecordSetWriterFactory

Implementations:
AvroRecordSetWriter
CSVRecordSetWriter
FreeFormTextRecordSetWriter
JsonRecordSetWriter
RecordSetWriterLookup
ScriptedRecordSetWriter
XMLRecordSetWriter
The Record Writer to use for serializing Records before writing them to a FlowFile.

This property is only considered if:
  • the property Record Reader has a value specified
Output Strategy *output-strategyUse Content as Value
  • Use Content as Value
  • Use Wrapper
  • Use Appender
The format used to output the JMS message into a FlowFile record.

This property is only considered if:
  • the property Record Reader has a value specified
JNDI Initial Context Factory Classjava.naming.factory.initialThe fully qualified class name of the JNDI Initial Context Factory Class (java.naming.factory.initial).

Supports Expression Language, using Environment variables.
JNDI Provider URLjava.naming.provider.urlThe URL of the JNDI Provider to use as the value for java.naming.provider.url. See additional details documentation for allowed URL schemes.

Supports Expression Language, using Environment variables.
JNDI Name of the Connection Factoryconnection.factory.nameThe name of the JNDI Object to lookup for the Connection Factory.

Supports Expression Language, using Environment variables.
JNDI / JMS Client Librariesnaming.factory.librariesSpecifies jar files and/or directories to add to the ClassPath in order to load the JNDI / JMS client libraries. This should be a comma-separated list of files, directories, and/or URLs. If a directory is given, any files in that directory will be included, but subdirectories will not be included (i.e., it is not recursive).

Supports Expression Language, using Environment variables.
JNDI Principaljava.naming.security.principalThe Principal to use when authenticating with JNDI (java.naming.security.principal).

Supports Expression Language, using Environment variables.
JNDI Credentialsjava.naming.security.credentialsThe Credentials to use when authenticating with JNDI (java.naming.security.credentials).
JMS Connection Factory Implementation ClasscfThe fully qualified name of the JMS ConnectionFactory implementation class (eg. org.apache.activemq.ActiveMQConnectionFactory).

Supports Expression Language, using Environment variables.
JMS Client LibrariescflibPath to the directory with additional resources (eg. JARs, configuration files etc.) to be added to the classpath (defined as a comma separated list of values). Such resources typically represent target JMS client libraries for the ConnectionFactory implementation.

Supports Expression Language, using Environment variables.
JMS Broker URIbrokerURI pointing to the network location of the JMS Message broker. Example for ActiveMQ: 'tcp://myhost:61616'. Examples for IBM MQ: 'myhost(1414)' and 'myhost01(1414),myhost02(1414)'.

Supports Expression Language, using Environment variables.
JMS SSL Context ServiceSSL Context ServiceController Service:
SSLContextService

Implementations:
StandardRestrictedSSLContextService
StandardSSLContextService
The SSL Context Service used to provide client certificate information for TLS/SSL connections.

Dynamic Properties

NameValueDescription
The name of a Connection Factory configuration property.The value of a given Connection Factory configuration property.Additional configuration property for the Connection Factory. It can be used when the Connection Factory is being configured via the 'JNDI *' or the 'JMS *'properties of the processor. For more information, see the Additional Details page.

Supports Expression Language: Yes, evaluated using Environment variables.

Relationships

NameDescription
parse.failureIf a message cannot be parsed using the configured Record Reader, the contents of the message will be routed to this Relationship as its own individual FlowFile.
successAll FlowFiles that are received from the JMS Destination are routed to this relationship

Reads Attributes

This processor does not read attributes.

Writes Attributes

NameDescription
jms.messagetypeThe JMS message type, can be TextMessage, BytesMessage, ObjectMessage, MapMessage or StreamMessage).
jms_correlationIdThe JMSCorrelationID from the message header.
jms_deliveryModeThe JMSDeliveryMode from the message header.
jms_destinationThe JMSDestination from the message header.
jms_expirationThe JMSExpiration from the message header.
jms_messageIdThe JMSMessageID from the message header.
jms_priorityThe JMSPriority from the message header.
jms_redeliveredThe JMSRedelivered from the message header.
jms_replyToThe JMSReplyTo from the message header.
jms_timestampThe JMSTimestamp from the message header.
jms_typeThe JMSType from the message header.
other attributesEach message property is written to an attribute.

State Management

This component does not store state.

Restricted

Required PermissionExplanation
reference remote resourcesClient Library Location can reference resources over HTTP

Input Requirement

This component does not allow an incoming relationship.

System Resource Considerations

This component does not specify system resource considerations.

See Also

JMSConnectionFactoryProvider, PublishJMS