All Apps and Add-ons

JMS Modular Input: message_handler_impl setting not calling associated jar

jpressley_splun
Splunk Employee
Splunk Employee

I am having an issue JMS Modular input the following are my settings for inputs.conf. The issue i am having is that it appears that the message_handler_impl setting is not being triggered. Does anyone have any ideas as to why this may be happening

[jms://queue/REDACTED]
browse_mode = all
browse_queue_only = 0
durable = 0
index_message_header = 0
index_message_properties = 1
init_mode = jndi
jms_connection_factory_name = REDACTED_JNDI
jndi_initialcontext_factory = com.sun.jndi.fscontext.RefFSContextFactory
jndi_provider_url = file:/splunk/etc/apps/jms_ta/JNDI-Directory/REDACTED
sourcetype = queue_data
strip_newlines = 1
disabled = 0
browse_frequency = -1
index = queue_index
message_handler_impl = com.splunk.modinput.jms.custom.handler.JMSConvertToBinary
message_handler_params = msg.format.dir=/splunk/etc/apps/jms_ta/data

0 Karma

jpressley_splun
Splunk Employee
Splunk Employee

No, unfortunately there are not logs for this issue being generated. I have also experimented with various jars some of which are only calling the DefaultMessageHandler through object reference, to no avail.

0 Karma

Damien_Dallimor
Ultra Champion

Any logs ?

index=_internal ExecProcessor error jms.py

0 Karma
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...