A instalação padrão do Oracle Fusion Middleware falha no início do SOA ManagedServer devido a problemas de caminho de classe

1

Tentando instalar o Oracle Fusion Middleware 11gR2 no Windows (a mesma coisa acontece no Linux). Eu segui as diretrizes fornecidas no link

  1. Instalando o weblogic (11g)
  2. Instalação do Oracle 11g databse
  3. Executando o utilitário RCU para criar esquema
  4. Arquivos relevantes instalados e copiados para o Java Bridge
  5. Configure o Fusion Middleware

Mas descobri que o servidor SOA não está se levantando no gerenciador da empresa, mostrando-o como inativo. Quando eu chequei os logs iam recebendo o seguinte erro:

oracle.jrf.wls.JRFStartup java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup  
at java.lang.Class.forName0(Native Method)  
at java.lang.Class.forName(Class.java:247)  
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:253)  
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)  
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)  
Truncated. see log file for complete stacktrace  

<Jul 7, 2009 4:18:48 PM CEST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "SOAStartupClass", java.lang.ClassNotFoundException: oracle.bpel.services.common.util.GenerateBPMCryptoKey  
java.lang.ClassNotFoundException: oracle.bpel.services.common.util.GenerateBPMCryptoKey  
at java.lang.Class.forName0(Native Method)  
at java.lang.Class.forName(Class.java:247)  
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:253)  
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)  
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)  
Truncated. see log file for complete stacktrace  

<Jul 7, 2009 4:19:27 PM CEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'SocketAdapter' due to error weblogic.application.ModuleException: The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.socket.SocketConnectionFactory' could not be loaded from the resource adapter archive/application because of the following error:  
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory.weblogic.application.ModuleException: The ra.xml <connectionfactory-impl-class>  
class 'oracle.tip.adapter.socket.SocketConnectionFactory' could not be loaded from the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:228)  
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)  
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)  
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)  
Truncated. see log file for complete stacktrace
<Jul 7, 2009 4:19:27 PM CEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'MQSeriesAdapter' due to error weblogic.application.ModuleException: The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.mq.ConnectionFactoryImpl' could not be loaded from the resource adapter archive/application because of the following error:  
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory.weblogic.application.ModuleException: The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.mq.ConnectionFactoryImpl' could not be loaded from the resource adapter archive/application because of the following error:  
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory  
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:228)  
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)  
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)  
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)  
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)  
Truncated. see log file for complete stacktrace
<Jul 7, 2009 4:19:27 PM CEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'OracleAppsAdapter' due to error  
weblogic.application.ModuleException: java.lang.NoClassDefFoundError: oracle/tip/adapter/api/exception/PCResourceException.weblogic.application.ModuleException:  
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/exception/PCResourceException
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:238)  
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)  
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)  
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)  
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)  
Truncated. see log file for complete stacktrace  
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/exception/PCResourceException  
at java.lang.Class.getDeclaredMethods0(Native Method)  
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)  
at java.lang.Class.privateGetPublicMethods(Class.java:2547)  
at java.lang.Class.getMethods(Class.java:1410)  
at weblogic.connector.external.impl.RAComplianceChecker.checkOverrides(RAComplianceChecker.java:972)  
Truncated. see log file for complete stacktrace  

Alguém por favor pode me dizer se eu perdi alguma etapa?

    
por Neuquino 18.03.2010 / 15:37

1 resposta

1

A solução é definir StartScriptEnabled = true em $ WL_HOME / common / nodemanager / nodemanager.properties e reiniciar o NodeManager.

    
por 18.03.2010 / 15:39