Geek Answers Handbook

Why is triggerJob disabled in Quartz JMX?

I have successfully configured our application to export Quartz MBeans to JMX and can view everything in JConsole. I can do most scheduler operations.

The one I really want to run is "triggerJob", but it appears in the JConsole as greyed-out / disabled, so I cannot run it.

I looked at the commits that added the JMX code to Quartz, but I don't see the difference between triggerJob and other included operations.

Does anyone know what is going on?

EDIT - Description Found

Another StackOverflow problem describes what happens: Why are some methods on JConsole disabled

triggerJob (and two other operations) accept non-primitive parameters; these complex parameters cannot be provided in JConsole.

I don't understand if the MBean provider can provide a custom editor for JConsole (or simlar), but at least I have my answer.

+5
source share
1 answer

Thanks for your explanation. I successfully deleted the job remotely through JMX using the following Groovy code:

def callParams = new Object[3]
callParams[0] = 'com.test.project.TestJob'
callParams[1] = 'DEFAULT_JOB_GROUP'
callParams[2] = new HashMap()

def callSignature = new String[3]
callSignature[0] = 'java.lang.String'
callSignature[1] = 'java.lang.String'
callSignature[2] = 'java.util.Map'

// server is an instance of MBeanServerConnection
server.invoke('triggerJob', callParams, callSignature)
+1
source

More articles:


All Articles