"Failed to retrieve RMIServer stub" Error Received when Creating EDQ Data Server in DIPC-C Governance Edition ODI Studio Client
(Doc ID 2480012.1)
Last updated on FEBRUARY 03, 2022
Applies to:
Data Integration Platform Cloud Classic - Version 17.3.5 and laterInformation in this document applies to any platform.
Symptoms
Data Integration Platform Cloud Classic (DIPC-C) Governance Edition comes with Oracle Data Integrator (ODI) Studio and Enterprise Data Quality (EDQ)
Within ODI Studio, a Data server needs to be created under the EDQ technology specifying Server Host, JMX Port, User, Password and Domain.
After specifying the values as below:
Server Host: localhost
JMX Port : 8090
User : <EDQ admin User>
Password : <EDQ admin User Password>
Domain : edq
The "Test Connection" button fails with the below error:
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost;
nested exception is:
java.net.ConnectException: Connection timed out (Connection timed out)]
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:369)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at com.sunopsis.dwg.tools.edq.EDQClientUtil.create(EDQClientUtil.java:63)
at com.sunopsis.dwg.tools.edq.EDQClientUtil.create(EDQClientUtil.java:41)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet$5.doInBackground(SnpsDialogTestConnet.java:353)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet$5.doInBackground(SnpsDialogTestConnet.java:336)
at oracle.odi.ui.framework.AbsUIRunnableTask.run(AbsUIRunnableTask.java:258)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:961)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost;
nested exception is:
java.net.ConnectException: Connection timed out (Connection timed out)]
at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:136)
at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:205)
at oracle.javatools.jndi.HashContext.lookup(HashContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1955)
at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1922)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:287)
... 8 more
Changes
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 |
Changes |
Cause |
Solution |
References |