icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading JMS Messaging Modular Input
SHA256 checksum (jms-messaging-modular-input_172.tgz) 644fbc6dba40da2fbcba68ea6db874afebe50258899f925686acaed63d1d17fb SHA256 checksum (jms-messaging-modular-input_171.tgz) 5586fb05946e0c14734d5fc90f39ae0d0491621b0e54316eabb5b7889239af05 SHA256 checksum (jms-messaging-modular-input_17.tgz) 4f0ee3fb111288a3b93db8effaf2f7d3b431be76d0cca685b8590430b1a3c735 SHA256 checksum (jms-messaging-modular-input_161.tgz) fe75b3e94b360d6a1d9e2821e755e0baadcc3ed71ae09454ae537fe1a81d1a20 SHA256 checksum (jms-messaging-modular-input_16.tgz) 93f717ed6e3a18c94d4559fa35035058c89bbe24c4b57c66d3151cd9d5489103 SHA256 checksum (jms-messaging-modular-input_151.tgz) 4bb8db8ede9196b932873511221aea08449eee4a3a28a76fb4f1052bcd184b50 SHA256 checksum (jms-messaging-modular-input_15.tgz) ae9acc6c8c8bc04933db0c8877d0d041711d2712e23a799a3d0e9c3cda422796 SHA256 checksum (jms-messaging-modular-input_14.tgz) 69e405d6a8bcee0dfd7070f9e5a4064ae9ceb6a63b540bd952de1deda6d07c46 SHA256 checksum (jms-messaging-modular-input_138.tgz) eddf633d33d87dd40daff0bb4fa156dc060e1959ccb8e874eb684c2200c20990 SHA256 checksum (jms-messaging-modular-input_137.tgz) 93aac8f2f416e3e24fe805132f844860be49947278e2295431357d539c56e2d6 SHA256 checksum (jms-messaging-modular-input_136.tgz) ed18d6cae9f6113564be06ab8a60dab9268f1d1ed180cb240dbc0097bf274fcf SHA256 checksum (jms-messaging-modular-input_135.tgz) aaaac66e44cc309a064081f6f3fd1339a8c0d3f571c21580461937cd23f7ebca SHA256 checksum (jms-messaging-modular-input_134.tgz) 13b1038177b4f823a983f7b4a43ab556431227460c386a116639e842c62bd181 SHA256 checksum (jms-messaging-modular-input_133.tgz) f66318548a3a95d6dfe85bcb3c9e8214407d9ed2ea143547f41adc18b3b2eb36 SHA256 checksum (jms-messaging-modular-input_132.tgz) b526f1219450108f798386544973660be742fa297b9b5bbbc3ced9a2012e0c37 SHA256 checksum (jms-messaging-modular-input_131.tgz) d0ef314bc04f3d62974de24c454849ee8cea84a469549b1622f7a6dff41e4ea2 SHA256 checksum (jms-messaging-modular-input_13.tgz) ea05a7f826e5ab8ed9017ff74d1787666e675584609290cac09e9ed71e9bc939 SHA256 checksum (jms-messaging-modular-input_122.tgz) d729eabe00ee7ec9178de02434ba6b2abe6f15dab69602a6bd524fd639800cc3 SHA256 checksum (jms-messaging-modular-input_121.tgz) 2cf7b25b4d8b42725c5e3c7b9c7c76ee82a1a866f5520e95a0b6727ecfbfc0c2 SHA256 checksum (jms-messaging-modular-input_12.tgz) e2dece709d7da38f9ac35d9459de930c32781a2abc53f2c6e8eec2cf550eeedf SHA256 checksum (jms-messaging-modular-input_115.tgz) 92bce2febba06295c4b39bfcdb18d762e0fb33e2e11f14d1edcebc9cfa5e97ec SHA256 checksum (jms-messaging-modular-input_114.tgz) 510d88adc27e4dfc56f6b26d7afde8219d55a281a6df2c20a1bf51f40968572f SHA256 checksum (jms-messaging-modular-input_113.tgz) 8e0c72d111feef96be6b70ee0dfd083d747452cdaf21cb1ccf17aa1f2345cc2f SHA256 checksum (jms-messaging-modular-input_112.tgz) 9b0176bcc05ea5dd9c7f25f2c1cd06eb441666b36cb1326b4aa441aff7f3eaf7 SHA256 checksum (jms-messaging-modular-input_111.tgz) 33d8e654f7d50d75d57af93120a4919bcb717eb762142f89638d17997015b385 SHA256 checksum (jms-messaging-modular-input_11.tgz) 57aad2687da23204d128b689cfd4fb1f9e86102c984215236c74e51df9526983 SHA256 checksum (jms-messaging-modular-input_103.tgz) efc3bcfb431ba5e8eae5cb6fc217baae553e3d3e53436355739e1c36d63a089e SHA256 checksum (jms-messaging-modular-input_102.tgz) 3ca05d0c86de207153701dd5adf9570b4c9d248599a71dc8d8a39824d205d68c SHA256 checksum (jms-messaging-modular-input_101.tgz) ba1a21793cccbf38962bf59e905100a8b6b096300a313cca3f960acecee538a5 SHA256 checksum (jms-messaging-modular-input_10.tgz) 69978d5fbcc76618a3357d400709a665e1457cd4ea6110f3c7a2a530a9e8e80b
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

JMS Messaging Modular Input

Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
This is a Splunk modular input add-on for polling message queues and topics via the JMS interface.
JMS is simply a messaging API and is a convenient means by which to write 1 modular input that can talk to several different underlying messaging providers : MQSeries(Websphere MQ), ActiveMQ, TibcoEMS, HornetQ, RabbitMQ,Native JMS, Weblogic JMS, Sonic MQ etc..

Splunk JMS Modular Input v1.7.2


This is a Splunk modular input add-on for polling message queues and topics via the JMS interface.

It implements the Splunk Modular Inputs Framework

Why JMS ?

JMS is simply a messaging API and is a convenient means by which to write 1 modular input that can talk to several different underlying messaging
providers : MQSeries(Websphere MQ), ActiveMQ, TibcoEMS, HornetQ, RabbitMQ,Native JMS, Weblogic JMS, Sonic MQ etc..
The modular input code is generic because it is programmed to the JMS interface.
You can then supply messaging provider specific jar files at runtime.
More details on JMS at Wikipedia


  • Splunk 5.0+
  • Java Runtime 1.7+
  • Supported on Windows, Linux, MacOS, Solaris, FreeBSD, HP-UX, AIX


  • Optionally set your JAVA_HOME environment variable to the root directory of you JRE installation.If you don't set this , the input will look for a default installed java executable on the path.
  • Untar the release to your $SPLUNK_HOME/etc/apps directory
  • Restart Splunk
  • If you are using a Splunk UI Browse to Settings -- Data Inputs -- JMS Messaging to add a new Input stanza via the UI
  • If you are not using a Splunk UI (ie: you are running on a Universal Forwarder) , you need to add a stanza to inputs.conf directly as per the specification in README/inputs.conf.spec. The inputs.conf file should be placed in a local directory under an App or User context.

Activation Key

You require an activation key to use this App. Visit http://www.baboonbones.com/#activation to obtain a non-expiring key

JNDI vs Local mode

For the most part you will setup your JMS connectivity using JNDI to obtain the remote JMS objects.
However, you can bypass JNDI if you wish and use local instantiation.
To this you must code an implementation of the com.splunk.modinput.jms.LocalJMSResourceFactory interface.
You can then bundle the classes in a jar file and place them in $SPLUNK_HOME/etc/apps/jms_ta/bin/lib
The configuration screen for creating a new JMS input allows you to choose local or jndi as the instantiation mode.
So choose local , and then you can specify the name of implementation class, as well as any declarative paramaters you want to pass in.


Any log entries/errors will get written to $SPLUNK_HOME/var/log/splunk/splunkd.log

These are also searchable in Splunk : index=_internal error jms.py

To turn on more verbose INFO level logging , set the logging level in the $SPLUNK_HOME/etc/apps/jms_ta/bin/jms.py script ie: ERROR , INFO

Third party jars

If you require specific JMS provider or JNDI Context implementation jars, then you can simply copy these to $SPLUNK_HOME/etc/apps/jms_ta/bin/lib

They will be automatically picked up upon restart

JVM Heap Size

The default heap maximum is 64MB.
If you require a larger heap, then you can alter this in $SPLUNK_HOME/etc/apps/jms_ta/bin/jms.py on line 95

JVM System Properties

You can declare custom JVM System Properties when setting up new input stanzas.
Note : these JVM System Properties will apply to the entire JVM context and all stanzas you have setup


  • JAVA_HOME environment variable is set or "java" is on the PATH for the user's environment you are running Splunk as
  • You are using Splunk 5+
  • You are using a 1.7+ Java Runtime
  • You are running on a supported operating system
  • Any 3rd party jar dependencies are present in $SPLUNK_HOME/etc/apps/jms_ta/bin/lib
  • Look for any errors in $SPLUNK_HOME/var/log/splunk/splunkd.log
  • Run this command as the same user that you are running Splunk as and observe console output : "$SPLUNK_HOME/bin/splunk cmd python ../etc/apps/jms_ta/bin/jms.py --scheme"
  • Your configuration parameters are correct for your JMS connection (check for typos, correct credentials, correct JNDI names etc...)
  • You DNS resolution for hostnames is correctly configured



Release Notes

Version 1.7.2
April 23, 2019

updated docs

Version 1.7.1
April 19, 2019

added trial key functionality

Version 1.7
March 28, 2019

docs updated

Version 1.6.1
June 3, 2018

minor manager xml ui tweak for 7.1

Version 1.6
May 27, 2018

Added an activation key requirement , visit http://www.baboonbones.com/#activation to obtain a free,non-expiring key
Docs updated
Splunk 7.1 compatible

Version 1.5.1
Sept. 2, 2016

Added a new message handler that just dumps the message body :

Version 1.5
Nov. 24, 2015

Minor HEC data handling tweaks

Version 1.4
Sept. 22, 2015

Added support to optional output to Splunk via a HEC (HTTP Event Collector) endpoint

Version 1.3.8
Feb. 11, 2015

Enabled TLS1.2 support by default.
Made the core Modular Input Framework compatible with latest Splunk Java SDK
Please use a Java Runtime version 7+
If you need to use SSLv3 , you can turn this on in bin/jms.py

Version 1.3.7
Sept. 17, 2014

Changed the point in the code where client ID is set for durable topic subscriptions

Version 1.3.6
Feb. 21, 2014

Added a LocalConnectionFactory for ActiveMQ

Version 1.3.5
Jan. 25, 2014

Added the ability to declare custom JVM System Properties in your stanzas

Version 1.3.4
Jan. 24, 2014

Minor cosmetic fix

Version 1.3.3
Jan. 24, 2014

Added system property javax.net.ssl.trustStorePassword to LocalMQConnectionFactory

Version 1.3.2
Jan. 23, 2014

Added a custom local JMS resource factory for Websphere MQ users that allows you to create a MQConnectionFactory class instance directly vs looking it up via JNDI.

The implementation class name you can declare in you stanza is : com.splunk.modinput.jms.custom.factory.LocalMQConnectionFactory

It depends on the MQ JMS jar files being in SPLUNK_HOME/etc/apps/jms_ta/bin/lib

Parameter values supported are (showing example values) :


You declare these in the stanza also in a key=value string , comma delimited :


Version 1.3.1
Nov. 9, 2013

Changed suffix to .spl
Removed field validation constraints when selecting local mode

Version 1.3
July 9, 2013

Updated configuration screen , hopefully it is simpler and more intuitive

Version 1.2.2
June 4, 2013

More verbose error logging ++ Removed usage of hostname for REST callbacks and replaced with localhost to alleviate issues where admins haven't setup local DNS correctly

Version 1.2.1
March 28, 2013

Added support for very large message payloads, basically a refactoring of the XML streaming output so that SplunkD can correctly process large message payloads

Version 1.2
Feb. 27, 2013

Refactored the core engine so that now you can declare a pluggable JMS Message handler.For the most part you'll probably just rely on the default message handler that is part of the mod input. But given that a message producer can basically put anything in the message payload, there may be scenarios where you need some custom handling for the raw message payload ,so this new features provides this flexibility.

Version 1.1.5
Feb. 21, 2013

Patched a hole whereby the "disabled" property is not passed to the Mod Input by SplunkD when it is first created

Version 1.1.4
Feb. 21, 2013

Added more detailed error logging (written to $SPLUNK_HOME/var/log/splunk/splunkd.log) for troubleshooting

Version 1.1.3
Feb. 20, 2013

Fixed a possible(in theory) race condition scenario at startup ++ Added support for Queue Browsing , user can choose browsing mode(dump all messages or output summary stats about the queue) and the browsing frequency.

Version 1.1.2
Feb. 17, 2013

Some core framework tweaks++Added config option so users can specify whether or not to strip newline characters from the message body

Version 1.1.1
Feb. 7, 2013

Added runtime support for solaris, aix, freebsd, hp-ux***Added support to prefix your destination name with a server identifier , which now makes it possible to setup jms stanzas that have the same destination name but on different servers

Version 1.1
Feb. 5, 2013

Added REST API polling calls to the mod input so that it can poll SplunkD for the enabled/disabled status of each queue/topic stanza and stop message polling threads accordingly or terminate the entire mod input process if all queue/topic stanzas have been disabled.Using the Splunk Java SDK v1.0 for the REST API call, hence splunk.jar is now included in this release.

Version 1.0.3
Jan. 17, 2013

Added better handling of Binary message types

Version 1.0.2
Dec. 27, 2012

Added support for providing user/pass for the topic/queue

Version 1.0.1
Dec. 19, 2012

Cosmetic fix, added screenshot.

Version 1.0
Dec. 18, 2012


Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2019 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.