My Oracle Support Banner

E1: SVM: Server Manager Agent Unable to Communicate With Weblogic Instance With Error "Couldn't get a JMX connection to the OWL mbean server type ''" (Doc ID 2905168.1)

Last updated on NOVEMBER 17, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.


WebLogic HTML instances JPS920 and JDV920, and AdminServer instance fail to connect from Server Manager. When logged into the Weblogic Server console, the server is up and running. Users can log in to the HTML instances (JDV920) without any errors, but the status is undetermined in Server Manager Console and the instances cannot be started or stopped.

The e1Agent log from the Weblogic server displays the following:

From a command prompt, the following command (that failed earlier as outlined in the above error message) completes successfully with message "Successfully connected to Admin Server..."

Command to run: 'E:\java\jdk8\bin\java -classpath E:\Oracle\Middleware\oracle_common\modules\;E:\Oracle\Middleware\wlserver\modules\features\wlst.wls.classpath.jar;E:\Oracle\Middleware\wlserver\server\lib\wljmxclient.jar;E:\Oracle\Middleware\wlserver\server\lib\weblogic.jar;E:\jde_home\SCFHA\lib\ManagementAgent_JAR.jar com.jdedwards.mgmt.targets.owl.utils.OWLEmbWlst connect('<user>','<password>','t3://<Admin_Console_Host>.com:7001')


Steps to reproduce

1. Sign in to Server Manage Console.
2. Click on the Oracle WebLogic Server managed instance type under Managed Instance.
3. On the Oracle WebLogic Server page, under WebLogic Domains, the managed servers listed show as 'Undetermined' or 'Stopped'.




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.