All Apps and Add-ons

JMS modular input - MQ data format

julietjake
Explorer

I'm using the JMS modular input to read IBM MQ messages from a queue.

The majority of the messages are read correctly, but if there is a message with a blank 'Data Format' in the RFH2 header, the message is placed to the back out queue with the exception in splunkd.log:

/splunk/etc/apps/jms_ta/bin/jms.py" Examine the message data and ensure that it is of the correct format to be parsed as an MQJMS Message.

Of course I can look to amend the source system so that the data format is set, but is there anyway within Splunk I can force a default format like MQSTR?

0 Karma
1 Solution

Damien_Dallimor
Ultra Champion

This error is thrown by the underlying WAS MQ JMS provider jars.

So it is not something addressable in the JMS Modular Input code or Splunk.

It appears a non-JMS / non-parseable message was placed on the queue.

More info on this error , code JMSCMQ0018

View solution in original post

Damien_Dallimor
Ultra Champion

This error is thrown by the underlying WAS MQ JMS provider jars.

So it is not something addressable in the JMS Modular Input code or Splunk.

It appears a non-JMS / non-parseable message was placed on the queue.

More info on this error , code JMSCMQ0018

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...