About oka

oka · ‎05-01-2026

I’m able to connect to the message broker and successfully consume messages. However, I’ve noticed that some information—specifically contentType and contentEncoding—is missing. From what I understand, these fields are often treated as “private” since the Qpid JMS client does not provide a public API to set them directly. As I’m building an enterprise bridge using Apache Nifi, I want to preserve the original contentType and contentEncoding values when republishing the same message to another broker. May I know how to do it?

oka · ‎04-24-2026

I noticed that the Content-Type and Content-Encoding headers are missing after using ConsumeJMS. Is this expected behavior? Since I’m implementing a message bridge, I’d like to preserve and pass along the same Content-Type and Content-Encoding values to the target broker. How can I achieve this?

oka · ‎04-24-2026

1) 2.2.0 2) However, I didn’t notice any content-type or content-encoding attributes in the FlowFile within consumeJMS. JMSXDeliveryCount 1 filename 576fb206-3a78-4330-b85e-2c7215f57702 jms.messagetype TextMessage jms.source.destination q/mal/test/dev/test-abc jms_deliveryMode 2 jms_destination t/mal/test/dev/test-abc/v1/test jms_expiration 0 jms_messageId ID:AMQP_NO_PREFIX:a25814dd-3135-4733-8378-bd8348f4ebbb jms_priority 4 jms_redelivered false jms_timestamp 1777010201098 path ./ uuid 576fb206-3a78-4330-b85e-2c7215f56602

oka · ‎03-10-2026

During testing of the Enterprise Message Bridge implemented using Apache NiFi, it was identified that the Content-Type header becomes null when messages are routed from Message Broker A to Message Broker B. The bridge is designed to enable message flow between the two brokers using Apache NiFi as the intermediary integration layer. However, while validating message headers at the destination broker, the Content-Type attribute is not being preserved and is received as null. This behavior was observed during message inspection at the consumer side connected to Broker B. May I know how to preserve message Content-Type attribute/properties ? Using : ConsumeJMS and PublishJMS Protocol: AMQP 1.0

Online	Offline
Last Visited	‎05-13-2026 01:19 AM

Member Since	‎03-10-2026 08:16 AM
Last Visited	‎05-13-2026 01:19 AM
Posts	5

Cloudera Community

Re: Content-Type becomes null when bridging messag...

Re: Content-Type becomes null when bridging messag...

Re: Content-Type becomes null when bridging messag...

Content-Type becomes null when bridging messages f...