My Oracle Support Banner

OCI Stack Monitoring: On Windows 2022 Process Scheduler Discovery Fails (Doc ID 3008658.1)

Last updated on APRIL 11, 2024

Applies to:

OCI Stack Monitoring - Version N/A and later
Information in this document applies to any platform.

Symptoms

On OCI Stack Monitoring, Peoplesoft Process Scheduler  on the Windows host discovery fails with below error

The following resources could not be discovered: abcdecg_app_ProcessSchedulerGroup_abcdecg_psuat (Type: oracle_psft_prcs, Work Item Id: wi-xxxxxx-6f40-470e-97a7-b9761677585c), abcdefg_app_ProcessSchedulerGroup_abcdefg_psuat (Type: oracle_psft_prcs, Work Item Id: wi-xxxxxx), cdcpsuat1l01_app_ProcessSchedulerGroup_xxxxxxx_psuat (Type: oracle_psft_prcs, Work Item Id: wi-xxxxxxxxxx). Please find more details in the discovery job log below.

JMX Connection Test fails from Management Agent to Process Scheduler domain.

# java -jar jmxterm-1.0.2-uber.jar --url service:jmx:rmi:///jndi/rmi://<hostname>:<JMX_PORT>/psuat/DomainRuntime/DefaultConnector --user admin --password xxxxxxxx
Picked up _JAVA_OPTIONS: -Djava.security.egd=file:/dev/./urandom
Delete /home/psadm2/.jmxterm_history if you encounter error right after launching me.
Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: psuat/DomainRuntime/DefaultConnector
at java.management.rmi/javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:370)
at java.management/javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at org.cyclopsgroup.jmxterm.cc.SessionImpl.doConnect(SessionImpl.java:63)
at org.cyclopsgroup.jmxterm.cc.SessionImpl.connect(SessionImpl.java:38)
at org.cyclopsgroup.jmxterm.cc.CommandCenter.connect(CommandCenter.java:92)
at org.cyclopsgroup.jmxterm.boot.CliMain.execute(CliMain.java:134)
at org.cyclopsgroup.jmxterm.boot.CliMain.main(CliMain.java:41)
Caused by: javax.naming.NameNotFoundException: psuat1/DomainRuntime/DefaultConnector
at jdk.naming.rmi/com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:135)
at java.naming/com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:220)
at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)

 

Cause

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
Symptoms
Cause
Solution
References


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