在weblogic安装应用后报异常 'java.lang.NoClassDefFoundError: oracle/dms/http/Request' 处理方法...

最新推荐文章于 2024-06-23 09:29:56 发布

最新推荐文章于 2024-06-23 09:29:56 发布 · 442 阅读

文章标签：

本文详细介绍了如何解决WebLogic部署应用时出现的NoClassDefFoundError错误，原因是节点管理器中的JAR包未被重新加载。通过更新nodemanager.properties文件并设置StartScriptEnables=true，确保在运行节点管理器前加载必要的JAR包。同时，建议运行setNMProps脚本，重启节点管理器服务，重新启动ADF管理服务器，并确认部署已成功。确保部署目标正确配置于Admin Server和ADF Managed Server。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.html

使用以上官方文档安装后，直接安装应用会出现以下错误

<Error> <Deployer> <UNIBRAU> <adfserver1> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <4434b55da0f9041e:755c3f1:12f4a4c22dd:-8000-0000000000000b3d> <1302639266661> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1302639261332' for task 'weblogic.deploy.configChangeTask.1'. Error is: 'java.lang.NoClassDefFoundError: oracle/dms/http/Request'
java.lang.NoClassDefFoundError: oracle/dms/http/Request
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)

其实原因就是节点管理器中的JAR包没有被重新加载

有人用这种方法解决了

So far, I have resolved the above error buy updating nodemanager.properties file

I have set the StartScriptEnables=true

This will load the StartWeblogic.cmd file before running node manager (i believe) so necessary jars are loaded and after that if you apply JRF template, it works fine.

还有人建议以下方法

1) Run setNMProps script

For Windows installations: <MW_HOME>\oracle_common\common\bin\setNMProps.cmd
For Linux/Unix installations: <MW_HOME>/oracle_common/common/bin/setNMProps.sh

2) Restart the NodeManager process

For Windows installations: Stop and start the NodeManager Windows Service
For Linux/Unix installations: Stop nodemanager process by killing it and restart it with <MW_HOME>/wlserver_10.3/server/bin/startNodeManager.sh script

3) Restart the ADF Managed Server and verify that the same error is no longer reported .

4) Confirm in Admin Console that the DMS application is targeted to both the AdminServer and the ADF "Managed Server".

From Admin Console:
- Click in the Deployments section in the left panel
- Locate the application "DMS Application(11.1.1.1.0)" and validate its status is "Active"
- Click on the link in the application name "DMS Application(11.1.1.1.0)", and navigate to the "Targets"
- Verify that both AdminServer and the ADF "Managed Server" are listed

5) Start DMS application if not already started then access http://<host>:<managed server port>/dms/ and confirm dms application is working as expected.