WLS_FORMS Service Failed After Adding BASE_DOMAIN For Other Application (Doc ID 1638711.1)

Last updated on MAY 08, 2023

Applies to:

Symptoms

In Oracle Forms 11.1.2.0, after adding a new BASE_DOMAIN domain for another application, the WLS_FORMS services under original ClassicDomain domain cannot be restarted. The WLS_FORMS service still starts in ADMIN mode. 

Even restoring the server back to pre BASE_DOMAIN, the WLS_FORMS service still starts up in ADMIN mode.

The error message in the WLS_FORMS.out is as follows :

<Mar 12, 2014 11:37:44 AM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'formsapp [Version=11.1.2]' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.forms.config.FormsappLifeCycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace

Changes

 Add new domain (i.e. BASE_DOMAIN) for other application.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.