Solving weblogic.descriptor.descriptorexception

If you are getting below errors in log files then please follow mentioned steps in this post to help resolve the issue:

<BEA-000386> <Server subsystem failed. Reason: weblogic.descriptor.DescriptorValidateException: The following failures occurred:
-- Reference to Notification by [TPDomain]/AppDeployments[MyApp]/Targets is ambiguous;
The following beans share this name:
- weblogic.management.configuration.ServerMBeanImpl@37141746([TPDomain]/Servers[Notification])
- weblogic.management.configuration.ClusterMBeanImpl@37141747([TPDomain]/Clusters[Notification])

weblogic.descriptor.DescriptorValidateException: The following failures occurred:
-- Reference to Notification by [TPDomain]/AppDeployments[MyApp]/Targets is ambiguous;
The following beans share this name:
- weblogic.management.configuration.ServerMBeanImpl@37141746([TPDomain]/Servers[Notification])
- weblogic.management.configuration.ClusterMBeanImpl@37141747([TPDomain]/Clusters[Notification])

The above problem usually comes when there is some common names in configuration. Each server within a domain must have a name that is unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely.

Follow below steps to solve the issue:

1. Create a new managed server( Ignore if already created)

When you create a domain, you also create an Administration Server, which runs the Administration Console and distributes configuration changes to other servers in the domain. In a typical production environment, you create one or more Managed Servers in the domain to host business applications and use the Administration Server only to configure and monitor the Managed Servers.

To create a Managed Server in an existing domain:

– If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit
– In the left pane of the Console, select Environment > Servers.
– In the Servers table, click New.
– On the Create a New Server: Server Properties page:
— Enter the name of the server in the Name field.
— Each server within a domain must have a name that is unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.
— The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.
— In Listen Address, if you want to limit the valid addresses for a server instance, enter an IP address or DNS name. Otherwise, URLs to the server can specify any of the host computer’s IP address, any DNS name that maps to one of the IP addresses, or the localhost string.
— In Listen Port, enter the port number from which you want to access the server instance.
— If you run multiple server instances on a single computer, each server must use its own listen port.
— Specify whether or not this server will be a stand alone server or will belong to a cluster.
— If this server is part of a cluster:
— Select an existing cluster from the drop down list.
— Select the button to create a new cluster
— Click Next.
— Review the configuration options you have chosen.
— Click Finish.
– To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
– Not all changes take effect immediately—some require a restart

2. Stop any managed servers, then the admin server.
3. Back up the $DOMAIN_HOME/config/config.xml file.
4. Edit the config.xml file to make sure that all configuration objects in the domain are named uniquely.
5. Remove any other copies of config.xml, for example, from $DOMAIN_HOME/config/pending.
6. Restart the admin server, then any managed servers.
The above steps should solve the issue.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.