Error "RuntimeException: Updates to config files not supported" Extending Oracle Enterprise Repository WebLogic Domain to Include Oracle Service Registry.
(Doc ID 1288698.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Service Registry - Version 11.1.1.2.0 to 11.1.1.2.0 [Release Oracle11g]Information in this document applies to any platform.
Symptoms
You are attempting to extend an existing Oracle Enterprise Repository (OER) WebLogic Server domain to include Oracle Service Registry (OSR), both OER and OSR releases are 11.1.1.2.0. This is described in OSR 11.1.1.2.0 documentation:
http://download.oracle.com/otndocs/tech/soa/OSR11gR1ProductDocumentation.pdf
Starting on page 45, it shows extending an existing domain that already has OER installed in it.
Attempting to install into a separate server in the domain, or the same server as OER fails with the
following example error trace:
org.idoox.wasp.WaspInternalException: java.lang.RuntimeException: Updates to config files not supported
at com.systinet.wasp.WaspImpl.boot(WaspImpl.java:399)
at org.systinet.wasp.Wasp.init(Wasp.java:151)
at com.systinet.transport.servlet.server.Servlet.init(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
cuteThread.run(ExecuteThread.java:176)
Also the workaround listed in the following document does not work:
OSR Installation Fails With Java.Lang.Runtimeexception: Updates To Config Files Not Supported When Just Part Of The SMTP Details Are Provided [ID 1091903.1]
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 |