Hi
I'm trying to establish a JMX connection to a secured WebSphere instance by use of a direct URL. The final XML config that I'm using is:
<jmxpoller>
<formatter className="com.dtdsoftware.splunk.formatter.TokenizedMBeanNameQuotesStrippedFormatter" />
<cluster name="cluster" description="A cluster">
<mbean domain="WebSphere" properties="*,type=JVM,j2eeType=JVM" dumpAllAttributes="true" ></mbean>
<jmxserver jmxServiceURL="service:jmx:iiop://<host>:<port>/jndi/JMXConnector" jmxaccount="_Splunk_TA_jmx_account_#Splunk_TA_jmx#<account>" jvmDescription="A test" />
</cluster>
</jmxpoller>
(Host port and account values are all real, just redacted in this post).
A test of this jmxServiceURL is successful using my own quick Java program to verify, but the URL does not work within Splunk_TA_JMX.
It appears to fall down in some kind of URL parsing stage:
2016-04-04 15:08:34,335 - com.splunk.modinput.ModularInput -121182 [Thread-9] ERROR - cannot create JMXServiceURL for server with description A test - For input string: "<port>/jndi"
The reported input string ( <port>/jndi ) has been stripped down to just the port and stub, missing the rest of the URL.
I understand this URL format is different to that suggested in Splunk WAS addon, but this is for a secured WebSphere instance which will not work with those instructions. This URL format should work with a secured instance as long as the correct SSL/SAS properties are set and -Djmx.remote.protocol.provider.pkgs=com.ibm.websphere.management.remote is also set, which I have done with a change to jmx.py. I'm fairly confident it will work if I can get the correct jmxServiceURL passed into the input.
... View more