MQ had a pre built sample applications that connected to MQ over JMS.I plugged in the same parameters as the bindings file that I generated.
Error:
06-06-2014 10:10:47.165 -0500 INFO ExecProcessor - Ran script: python /splunk/etc/apps/jms_ta/bin/jms.py, took 11.83 seconds to run, 0 bytes read, exited with code 2
06-06-2014 10:10:57.539 -0500 ERROR ModularInputs -
06-06-2014 10:10:57.601 -0500 INFO ExecProcessor - New scheduled exec process: python /splunk/etc/apps/jms_ta/bin/jms.py
06-06-2014 10:10:59.240 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" Stanza jms://queue/middlewarelogging:SPLUNK.LOGGING.PROCESSING : Error connecting : java.lang.ClassCastException: javax.naming.Reference cannot be cast to javax.jms.ConnectionFactory
06-06-2014 10:10:59.240 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" at com.splunk.modinput.jms.JMSModularInput$MessageReceiver.connect(Unknown Source)
06-06-2014 10:10:59.240 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" at com.splunk.modinput.jms.JMSModularInput$MessageReceiver.run(Unknown Source)
06-06-2014 10:10:59.784 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" Can't connect to Splunk REST API with the token [Splunk 607c6a4596d090048a261a1b7fd7311f], either the token is invalid or SplunkD has exited : HTTP 404 -- In handler 'jms': Invalid custom action for this internal handler (handler: jms, custom action: middlewarelogging:SPLUNK.LOGGING.PROCESSING, eai action: list).
06-06-2014 10:11:09.271 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" Stanza jms://queue/middlewarelogging:SPLUNK.LOGGING.PROCESSING : Error connecting : java.lang.ClassCastException: javax.naming.Reference cannot be cast to javax.jms.ConnectionFactory
06-06-2014 10:11:09.271 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" at com.splunk.modinput.jms.JMSModularInput$MessageReceiver.connect(Unknown Source)
06-06-2014 10:11:09.271 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" at com.splunk.modinput.jms.JMSModularInput$MessageReceiver.run(Unknown Source)
06-06-2014 10:11:09.787 -0500 ERROR ExecProcessor - message from "python /splunk/etc/apps/jms_ta/bin/jms.py" It has been determined via the REST API that all inputs have been disabled
06-06-2014 10:11:10.046 -0500 INFO ExecProcessor - Ran script: python /splunk/etc/apps/jms_ta/bin/jms.py, took 11.58 seconds to run, 0 bytes read, exited with code 2
save ATT39575.bindings as .bindings and try again.
hi dallimore, thanks for your response
currently after adding all the jar i am getting the following exception ..
Using IVTRun, I am getting the following exception which is consistent with the error we are getting in Splunk.
C:\Program Files (x86)\IBM\WebSphere MQ\java\bin>IVTRun -url "file:/c:/temp/mqjndii/ATT39575.bindings" -icf com.sun.jndi.fscontext.RefFSContextFactory
[watcher]started
5724-H72, 5655-R36, 5724-L26, 5655-L82 (c) Copyright IBM Corp. 2008. All Rights Reserved.
WebSphere MQ classes for Java(tm) Message Service
Installation Verification Test
Running com.ibm.mq.jms.MQJMSIVT from file:/C:/Program%20Files%20(x86)/IBM/WebSphere%20MQ/java/lib/com.ibm.mqjms.jar
Using administered objects, please ensure that these are available
Cannot create InitialContext! Please check your JNDI settings
javax.naming.NameNotFoundException; remaining name 'c:\temp\mqjndii\ATT39575.bindings'
C:\Program Files (x86)\IBM\WebSphere MQ\java\bin>
It is more or less impossible to figure out what your misconfiguration issue is based on that error dump , but It would appear you have some fundamental errors in your basic setup, either in the JMS settings you have provided or in you MQ setup.
Have you read this and followed the steps verbatim for MQ ?
You require all the jars as documented by way of the screenshot in the blog.
I have followed the procedure in that link.
but i have a doubt , do we need all the jar files mentioned in screen shot or just the 4 jar files.
currently i have added these 4 jar files.
jmsmodinput.jar
jms.jar
splunk.jar
log4j-1.2.16.jar