weblogic.application.ModuleException: Context path '' is already in use by the module: / application:

你。 提交于 2019-12-30 17:33:13

问题


When i am trying to run weblogic server 12c , it is throwing this error and is unable to start.

    <Apr 16, 2013 2:42:57 PM IST> <Warning> <HTTP> <BEA-101384> <WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:acsportal@acs-portal.war, Class:oracle.adfinternal.view.faces.activedata.AdsServlet>
    <Apr 16, 2013 2:42:58 PM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application "acsportal" due to error weblogic.application.ModuleException: Context path '' is already in use by the module: / application: acs-portal
    weblogic.application.ModuleException: Context path '' is already in use by the module: / application: acs-portal
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
            at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
            at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
            Truncated. see log file for complete stacktrace


Caused By: weblogic.application.ModuleException: Context path '' is already in use by the module: / application: acs-portal

            at weblogic.servlet.internal.WebAppModule.validateContextPath(WebAppModule.java:1392)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:1238)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:723)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
            at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
            Truncated. see log file for complete stacktrace

After this error, the server hanged at this point

<Apr 16, 2013 2:43:58 PM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a Work Manager with name wm/ProvisionWorkManager. Dispatch policy wm/ProvisionWorkManager will map to the default Work Manager for the application acs-portal>

and is not starting after this line kindly help how to resolve this error.


回答1:


  1. Stop the weblogic server
  2. Remove all war files from the 'autodeploy' folder in weblogic.
  3. Then start the weblogic server again
  4. After that type the URL "http:// localhost:7001/console/" in browser
  5. Go to " Configure applications" link
  6. Then select previous projects and the go stop -> When work completes



回答2:


  1. Go to Weblogic's config.xml
  2. Locate all <app-deployment> sections.
  3. Delete them (you may want to backup it somewhere).

In my case it was more than thirty instances of our application:

<app-deployment>
    <name>deploy_ear_ear_exploded</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>*path_to_application*</source-path>
    <security-dd-model>DDOnly</security-dd-model>
  </app-deployment>



回答3:


For me works:

1) Uninstall all previous deployments (all ears)

2) Stop de server

3) Go to user_projects/domains/base_domain/servers/AdminServer/tmp and delete all content in this folder (you can back up the content)

4) Start and deploy




回答4:


  1. Start the server
  2. Go to deployments ( http://localhost:7001/console/console.portal?_nfpb=true&_pageLabel=AppDeploymentsControlPage )
  3. Remove war deployments
  4. Then restart, it should works



回答5:


I also had this issue with the following message :

Context path '/geff' is already in use by the module: /geff application: geff

I went to WebLogic Server --> Deployments. Here I had the 'geff' deployment. I deleted it, went into Eclipse --> 'Servers' view --> 'Add and Remove' on my server --> 'Add' the deployment I want.

And then it was solved.




回答6:


It happens to me because I manually deployed wls-cat.war in localhost:7001/console. But actually it's not necessary. When I tried to visit localhost:7001/wls-cat, weblogic is deploying wls-cat.war automatically. While the path '/wls-cat' has been occupied by the manually deployed wls-cat.war, it failed by the error:

Problem occurred while dispatching servlet request.

......

Caused By: weblogic.application.ModuleException: Context path '/wls-cat' is already in use by the module: wls-cat.war application: wls-cat

To fix it, just delete the manually deployed one(s), and visit localhost:7001/wls-cat Weblogic will deploy it.

So I suppose the main reason this error happens is the path has been used by another application. Check all the deployed applications in your console and delete them or change their package names.




回答7:


You may use the configuration wizard and recreate the Server. For the integrated server I deleted the whole DefaultDomain folder and JDeveloper recreate the Web Server again.




回答8:


use command: docker system prune Than just build and run all the containers again



来源:https://stackoverflow.com/questions/16033609/weblogic-application-moduleexception-context-path-is-already-in-use-by-the-m

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!