WSM-02461 : A document without a naming attribute cannot be written Error in Cluster-'wsm-pm' Fails in one managed server and starts in another
(Doc ID 2131590.1)
Last updated on DECEMBER 16, 2022
Applies to:
Oracle Web Services Manager - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
PROBLEM DESCRIPTION
--------------------
On an Oracle Management Server (OMS) cluster using Middleware 11.1.1.7, the wsm-pm application can start on the AdminServer and <OMS1> but not on <OMS2>. The schema repository was rebuilt using RCU and a new schema was created when this problem first occurred, but setting the data source to this new schema and restarting the application did not change the results.
The wsm-pm is targeted to all three servers. The mds-owsm data source is targeted to all servers and can connect successfully to the new MDS schema created.
The issue started after upgrading the failing managed server to 11.1.1.9. When looking at the application in the Weblogic Console, it shows as Active but when expanding it, a failure occurs producing the following error:
java.lang.IllegalArgumentException: WSM-02461 : A document without a naming attribute cannot be written.
at oracle.wsm.policymanager.bean.util.ManagedDocumentFactory.createManagedDocument(ManagedDocumentFactory.java:187)
at oracle.wsm.policymanager.bean.UpgradeManagerBean.updateExistingForRuntimeChange(UpgradeManagerBean.java:971)
at oracle.wsm.policymanager.bean.UpgradeManagerBean.upgradeWSMPolicyRepository_Internal(UpgradeManagerBean.java:884)
at oracle.wsm.policymanager.bean.UpgradeManagerBean.upgradeWSMPolicyRepository(UpgradeManagerBean.java:765)
at oracle.wsm.policymanager.web.PolicyManagerValidator.initializeWSMPM(PolicyManagerValidator.java:193)
Truncated. see log file for complete stacktrace
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 |