My Oracle Support Banner

Batch Job Monitoring (Doc ID 953282.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Utilities Framework - Version and later
Information in this document applies to any platform.


How we can kill a submitted batch job without bouncing the environment?
I tried to use -j service:jmx:rmi:///jndi/rmi://<HOSTNAME>:9999/spl/fw/jmxConnector
but it is not working.

<Patch 8515885> and <Patch 8222333> have been installed in the environment as per <Note 796100.1> and  <Note 850207.1>

Submitted the batch job from the command line and received "There are no jobs active":

service:jmx:rmi:///jndi/rmi://<HOSTNAME>:9999/spl/fw/jmxConnector -d
- 2009-10-06 13:56:59,363 [main] INFO (api.batch.JMXCommandLineClient) Options: -j
service:jmx:rmi:///jndi/rmi://<HOSTNAME>:9999/spl/fw/jmxConnector -d
- 2009-10-06 13:56:59,366 [main] INFO (api.batch.JMXCommandLineClient) Connecting to
- 2009-10-06 13:56:59,538 [main] INFO (api.batch.JMXCommandLineClient) ActiveGridNode
- 2009-10-06 13:56:59,539 [main] INFO (api.batch.JMXCommandLineClient)
threadPools=[LOCAL_THREAD_POOL:75b55b8f5f8f394e:-196ab335:12426761049:-8000:0, DEFAULT:8,
- 2009-10-06 13:56:59,539 [main] INFO (api.batch.JMXCommandLineClient)
- 2009-10-06 13:56:59,544 [main] INFO (api.batch.JMXCommandLineClient) There are no jobs active


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.