Migration von weblogic 9.2 auf 10.3.6 Fehler beim Laden von bea_wls9_async_response.war

Ich habe eine Anwendung von weblogic 9.2 auf weblogic 11 G (10.3.6) migriert. Während neue WebLogic Server gestartet haben, stehen wir Probleme auch Java-Version von jdk1.5 zu JDK aktualisiert wird 1,6Migration von weblogic 9.2 auf 10.3.6 Fehler beim Laden von bea_wls9_async_response.war

<12 déc. 2016 10 h 04 CET> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application E:\bea_10332\user_projects\domains\DOM\servers\Server\tmp\.internal\bea_wls9_async_response.war. Please make sure that the annotations are valid. The error is > 

<12 déc. 2016 10 h 04 CET> <Error> <J2EE> <LFR006114> <PhileasServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1481533463745> <BEA-160001> <Error deploying Internal Application: weblogic.application.ModuleException: Failed to load webapp: 'bea_wls9_async_response.war' 
    weblogic.application.utils.StateChangeException: weblogic.application.ModuleException: Failed to load webapp: 'bea_wls9_async_response.war' 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:67) 
     at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:273) 
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) 
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) 
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) 
    Caused By: weblogic.application.ModuleException: Failed to load webapp: 'bea_wls9_async_response.war' 
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395) 
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) 
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) 
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) 
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) 
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) 
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648) 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) 
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) 
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44) 
     at weblogic.application.internal.BackgroundDeploymentService$1.next(BackgroundDeploymentService.java:348) 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) 
     at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:273) 
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) 
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) 
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) 
    Caused By: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found 
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129) 
     at com.bea.core.repackaged.springframework.beans.factory.xml.DefaultDocumentLoader.createDocumentBuilderFactory(Unknown Source) 
     at com.bea.core.repackaged.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(Unknown Source) 
     at com.bea.core.repackaged.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(Unknown Source) 
     at com.bea.core.repackaged.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(Unknown Source) 
     at com.bea.core.repackaged.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(Unknown Source) 
     at com.bea.core.repackaged.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) 
     at com.bea.core.repackaged.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) 
     at com.bea.core.repackaged.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) 
     at com.oracle.pitchfork.server.DefaultContainerBootstrap.bootstrap(DefaultContainerBootstrap.java:51) 
     at com.oracle.pitchfork.server.Bootstrap.deploy(Bootstrap.java:147) 
     at com.oracle.pitchfork.spi.WLSBootstrap.deploy(WLSBootstrap.java:111) 
     at com.oracle.pitchfork.server.Bootstrap.deploy(Bootstrap.java:114) 
     at com.oracle.pitchfork.spi.bean.internal.AbstractBeanManager.initialize(AbstractBeanManager.java:52) 
     at com.oracle.pitchfork.spi.WebComponentContributorBrokerImpl.initialize(WebComponentContributorBrokerImpl.java:69) 
     at weblogic.servlet.internal.WebComponentContributor.initialize(WebComponentContributor.java:98) 
     at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1388) 
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:450) 
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494) 
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) 
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976) 
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384) 
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) 
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) 
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) 
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) 
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) 
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648) 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) 
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) 
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44) 
     at weblogic.application.internal.BackgroundDeploymentService$1.next(BackgroundDeploymentService.java:348) 
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) 
     at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:273) 
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) 
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) 
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Haben Sie eine Ahnung, was die Ursache dieser Spur ist oder wie kann ich es beheben bitte?

danke euch allen.

Quelle

2016-12-12 yobs

die Kommentare Siehe hier: http://stackoverflow.com/questions/34149546/java-lang-classnotfoundexception-org-apache- xerces-jaxp-documentbuilderfactoryi – Berger

Der Post in der Verbindung ist über eine ClassNotFound:/ – yobs

Der Stack-Trace ist abgeschnitten: "Abgeschnitten. Siehe Protokolldatei für komplette StackTrace", also schauen Sie sich die Protokolldatei an, wenn Sie das Ganze wollen Es hat gute Chancen, das gleiche Problem wie in der obigen Verbindung zu sein. – Berger

Vielleicht sollten Sie einige Anmerkungen, die ein Problem verursachen könnten, entfernen und die web.xml-Zuordnung anstelle von Anmerkungen verwenden.

Quelle

2016-12-12 10:00:25

Im Code die einzige Anmerkung, die ich habe, sind "param", "wirft" und "zurück" ich glaube nicht, dass es eine Auswirkung hat: / – yobs

here die Lösung meiner Probleme war (add xerces.jar in unterstützt Ordner)

Quelle

2016-12-13 09:57:22 yobs

Migration von weblogic 9.2 auf 10.3.6 Fehler beim Laden von bea_wls9_async_response.war

Antwort

Verwandte Themen