weblogic无法启动 在日志中找到 weblogic.security.spi.ResourceCreationException

最新推荐文章于 2021-05-16 13:19:33 发布
原创 最新推荐文章于 2021-05-16 13:19:33 发布 · 2.2k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#weblogic #磁盘 #linux

本文介绍了WebLogic服务因磁盘空间不足导致启动失败的问题及排查过程。通过简单的磁盘空间检查命令(df-h, df-k)，快速定位并解决了问题。

      weblogic服务突然挂掉，并且无法启动，最后找到weblogic.security.spi.ResourceCreationException异常，检查了下磁盘占用的空间才发现问题所在。

 

 

 

 

 

 

 

错误原因，磁盘空间不足！

linux下查看磁盘空间的命令：df -h ,df -k

ckstory
关注
50、WebLogic 安全架构中的认证与授权机制解析
y2z3a4b5c的博客
07-23 40
本文深入解析了 WebLogic 安全架构中的认证与授权机制，涵盖了 JAAS、PAM 框架、LoginContext 与 LoginModule 的工作流程、基于主体的访问控制（PBAC）、安全领域的配置与使用、WebLogic SPI 的功能扩展、WLEC 在企业连接中的应用等内容。同时，文章总结了认证与授权的最佳实践，并展望了未来 WebLogic 安全架构的发展趋势，为构建安全可靠的企业级应用系统提供了全面的技术指导。
WebLogic 之安全配置
qq_40907977的博客
07-20 4431
WebLogic 之安全配置 前段时间Java的反序列化漏洞吵得沸沸扬扬，因工作原因需要对weblogic进行安全配置，网上关于weblogic的安全配置的内容都不是很全面，可能是因为weblogic已经比较成熟了吧。 本文就总结一下在整个过程中遇到的一些坑，并给出正确的姿势。 1.最小化安装 1）禁止采用默认weblogic作为管理员用户名，建议采用不易被猜测的用户名，如“root_domain”等。 2）禁止采用示例应用 2.口令长度设置至少为8位 默认在安装时，weblogic要求密码至少为8位，但是
WebLogic Security
cnbird's blog
07-03 776
http://e-docs.bea.com/wls/docs81/secintro/index.html
weblogic Security:090310]Failed to create resource
yanbingwei_13
06-01 517
发布war包到weblogic中，日志报错： weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource.> Parsing failure for expression: Rol() Cannot generate test for empty list ...
重新启动WebLogic之前不生成日志文件
sinat_34966486的博客
11-27 538
重新启动WebLogic之前不生成日志文件 http://www.voidcn.com/article/p-gyovrkhv-bvt.html
weblogic启动日志详细说明
03-28
weblogic启动日志详细说明介绍，报错了所有的初始化信息模块的介绍！
weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". at weblogic.deploy.internal.adminserver.operations.OperationHelper.assertAppIsNonNull(OperationHelper.java:968) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.updateConfiguration(RemoveOperation.java:191) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.updateConfigurationAndInitializeDeployment(AbstractOperation.java:478) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:301) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.execute(RemoveOperation.java:84) at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:1034) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:137) at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:1028) at weblogic.management.deploy.internal.DeployerRuntimeImpl.undeploy(DeployerRuntimeImpl.java:513) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:532) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:249) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:439) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.MBeanCICInterceptor.invoke(MBeanCICInterceptor.java:304) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.PartitionJMXInterceptor.invoke(PartitionJMXInterceptor.java:435) at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:355) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.CallerPartitionContextInterceptor.invoke(CallerPartitionContextInterceptor.java:217) at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:327) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:655) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:653) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:646) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:645) at weblogic.rmi.internal.BasicServerRef$2.run(BasicServerRef.java:534) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:531) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:138) at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352) at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337) at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57) at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41) at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420) at weblogic.work.ExecuteThread.run(ExecuteThread.java:360) Unexpected Error Initializing Deployer: weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". ------------------------------------ ARTIFACT DEPLOYMENT ------------------------------------------------ weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name crm -source /root/.jenkins/workspace/TEST_FN_CRM/dist/crm.war -targets AdminServer -adminurl t3://10.190.252.34:80 -user weblogic -deploy [WebLogicDeploymentManagerImpl.<init>():112] : Constructing DeploymentManager for Java EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():155] : Connecting to admin server at 10.190.252.34:80, as user weblogic [ServerConnectionImpl.getEnvironment():317] : setting environment [ServerConnectionImpl.getEnvironment():320] : getting context using t3://10.190.252.34:80 [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.runtime [DomainManager.resetDomain():36] : Getting new domain [DomainManager.resetDomain():39] : Using pending domain: false [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [ServerConnectionImpl.initialize():193] : Connected to WLS domain: smecs [ServerConnectionImpl.setRemote():514] : Running in remote mode [ServerConnectionImpl.init():183] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@3ed242a4 [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: crm <Jul 17, 2025 8:25:59 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, crm [archive: /root/.jenkins/workspace/TEST_FN_CRM/dist/crm.war], to AdminServer .> [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.loadGeneralOptions():718] : Delete Files:false Timeout :3600000 Targets: AdminServer ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: /tmp/root/./config/deployments/crm App config: /tmp/root/./config/deployments/crm/plan Partition: null ResourceGroup: null Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=crm,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false,specifiedTargetsOnly=false,partition=null,resourceGroup=null,resourceGroupTemplate=null,uploadPath=null,specifiedModules=[],removePlanOverride=false,} 这个啥错？
07-18
但根据日志，系统似乎在部署前尝试先 **undeploy（卸载）** 旧版本的 `crm` 应用，这是 `-deploy` 参数的默认行为之一。 但由于 WebLogic 中并没有名为 `"crm"` 的应用，所以它抛出了 `[Deployer:149001]No ...
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:355) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:587) at weblogic.management.mbeanservers.internal.CallerPartitionContextInterceptor.invoke(CallerPartitionContextInterceptor.java:217) at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:327) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:655) at java.security.AccessController.doPrivileged(Native Method) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:653) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:646) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:645) at weblogic.rmi.internal.BasicServerRef$2.run(BasicServerRef.java:534) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:531) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:138) at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352) at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337) at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57) at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41) at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420) at weblogic.work.ExecuteThread.run(ExecuteThread.java:360) Unexpected Error Initializing Deployer: weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". ------------------------------------ ARTIFACT DEPLOYMENT ------------------------------------------------ weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name crm -source /root/.jenkins/workspace/TEST_FN_CRM/dist/crm.war -targets AdminServer -adminurl t3://10.190.252.34:80 -user weblogic -deploy [WebLogicDeploymentManagerImpl.<init>():112] : Constructing DeploymentManager for Java EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():155] : Connecting to admin server at 10.190.252.34:80, as user weblogic [ServerConnectionImpl.getEnvironment():317] : setting environment [ServerConnectionImpl.getEnvironment():320] : getting context using t3://10.190.252.34:80 [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.runtime [DomainManager.resetDomain():36] : Getting new domain [DomainManager.resetDomain():39] : Using pending domain: false [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [ServerConnectionImpl.initialize():193] : Connected to WLS domain: smecs [ServerConnectionImpl.setRemote():514] : Running in remote mode [ServerConnectionImpl.init():183] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@3ed242a4 [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: crm <Jul 17, 2025 8:25:59 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, crm [archive: /root/.jenkins/workspace/TEST_FN_CRM/dist/crm.war], to AdminServer .> [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.loadGeneralOptions():718] : Delete Files:false Timeout :3600000 Targets: AdminServer ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: /tmp/root/./config/deployments/crm App config: /tmp/root/./config/deployments/crm/plan Partition: null ResourceGroup: null Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=crm,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false,specifiedTargetsOnly=false,partition=null,resourceGroup=null,resourceGroupTemplate=null,uploadPath=null,specifiedModules=[],removePlanOverride=false,} 发服务器报错这是application.xml配置的问题吗？
07-18
这个错误 **不是由 `application.xml` 引起的**，而是 WebLogic 在部署过程中尝试执行 `undeploy` 操作时失败导致的。核心错误信息如下： ``` weblogic.management.ManagementException: [Deployer:149001]No ...
weblogic.Deployer invoked with options: -debug -remote -verbose -noexit -name crm -targets AdminServer -adminurl t3://10.190.252.34:80 -user weblogic -undeploy [WebLogicDeploymentManagerImpl.<init>():112] : Constructing DeploymentManager for Java EE version V1_4 deployments [WebLogicDeploymentManagerImpl.getNewConnection():155] : Connecting to admin server at 10.190.252.34:80, as user weblogic [ServerConnectionImpl.getEnvironment():317] : setting environment [ServerConnectionImpl.getEnvironment():320] : getting context using t3://10.190.252.34:80 [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.domainruntime [ServerConnectionImpl.getMBeanServer():268] : Connecting to MBeanServer at service:jmx:t3://10.190.252.34:80/jndi/weblogic.management.mbeanservers.runtime [DomainManager.resetDomain():36] : Getting new domain [DomainManager.resetDomain():39] : Using pending domain: false [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@2e2ff723 [MBeanCache.addNotificationListener():133] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [MBeanCache.addNotificationListener():140] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@7cf6a5f9 [ServerConnectionImpl.initialize():193] : Connected to WLS domain: smecs [ServerConnectionImpl.init():183] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@3ed242a4 [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.deriveAppName():143] : appname established as: crm <Jul 17, 2025 8:25:55 AM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, crm [archive: null], to AdminServer .> [BasicOperation.dumpTmids():811] : Incoming tmids: [BasicOperation.dumpTmids():813] : {Target=AdminServer, WebLogicTargetType=server, Name=crm}, targeted=true [BasicOperation.loadGeneralOptions():718] : Delete Files:false Timeout :3600000 Targets: AdminServer ModuleTargets={} SubModuleTargets={} } Files: null Deployment Plan: null App root: null App config: null Partition: null ResourceGroup: null Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=crm,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false,specifiedTargetsOnly=false,partition=null,resourceGroup=null,resourceGroupTemplate=null,uploadPath=null,specifiedModules=[],removePlanOverride=false,} [BasicOperation.execute():517] : Initiating undeploy operation for app, crm, on targets: [BasicOperation.execute():519] : AdminServer weblogic.management.ManagementException: [Deployer:149001]No application named "crm" exists for operation "undeploy". at weblogic.deploy.internal.adminserver.operations.OperationHelper.assertAppIsNonNull(OperationHelper.java:968) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.updateConfiguration(RemoveOperation.java:191) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.updateConfigurationAndInitializeDeployment(AbstractOperation.java:478) at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:301) at weblogic.deploy.internal.adminserver.operations.RemoveOperation.execute(RemoveOperation.java:84) at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:1034) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:137) at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:1028) at weblogic.management.deploy.internal.DeployerRuntimeImpl.undeploy(DeployerRuntimeImpl.java:513) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:532) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$21.run(WLSMBeanServerInterceptorBase.java:589) at java.security.AccessController.doPrivileged(Native Method)这是建构的什么报错，和application.xml有关系吗
最新发布
07-18
表示你尝试在 WebLogic Server 上执行 `undeploy` 操作时，系统找不到名为 `crm` 的应用。也就是说，WebLogic 服务器中当前并没有部署名为 `crm` 的应用程序。 --- ### 回答问题 #### 这个报错和 `application....
weblogic linux 停止报错,weblogic开启管理端口后停止报错
weixin_42548782的博客
05-16 2212
中间件环境如下：在weblogic console上开启Administration Port，如下图：此后用stopWebLogic.sh脚本去关闭AdminServer报错如下，[bea@mylinux bin]$ ./stopWebLogic.shStopping Weblogic Server…Initializing WebLogic Scripting Tool (WLST) …Wel...
关于weblogic对jndi的spi接口实现问题
我的2007
02-11 826
sun提供jndi规范，通过这个接口规范把名称和对象联系起来。但是怎么实现在于中间厂商对这个spi接口的实现。先看下面的代码：public static void main(String args[]){Properties properties = new Properties();properties.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.
weblogic11g无法启动，报Security:090399
寒江的专栏
09-15 7325
weblogic11g无法启动，报Security:090399 weblogic11g无法启动，报Security:090399 分类： 中间件     安装了oracle的weblogic11g for windows准备研究研究，创建一个domain后
weblogic无法启动
tongjie008的专栏
11-12 718
由于上级领导需要前来迎检，对某一系统进行漏洞
Weblogic系统管理学习笔记
Leon的测试小站
03-18 4287
<br /><br />WLS9/10 系统管理<br />----------------------------------------------------------------<br />教材：Weblgic Server9/10系统管理 指南第1册<br />进度：p65<br />----------------------------------------------------------------<br />域：WLS安装的基本管理单元：它是逻辑上相关的一组Weblogic Ser
linux启动weblogic，并且查看启动日志
热门推荐
rshw123456的专栏
01-03 4万+
cd /home/weblogic/Oracle/Middleware/user_projects/domains/newbase_domain   //进入到weblogic的启动日志 ps -ef | grep java   //看java进程 nohup ./startWebLogic.sh &  //启动weblogic进程 ail -f nohup.out
weblogic 日志介绍
CR7 - Xyy -- For oracle
08-20 5976
1.server.log  该日志记录的是服务（包括admin server 和 app server）启动过程中和关闭过程中的日志，还包括部署在服务上面的应用，在运行过程中所产生的日志. server.log 日志的路径一般在：domainname/servers/servername/logs/server.log(os系统上的位置) server.log的路径、名字、错误输出的等级是
weblogic启动报错分析
Andy成长空间
06-22 2043
weblogic启动出错，一般提示如下错误： Bean already exists:"weblogic.j2ee.descriptor.ListenerBeanImpl@69c61cb6(/Listeners[org.springframework.web.context.ContextLoaderListener])" Bean already exists: weblogic.j2ee.
weblogic启动报错异常解决
yuan29346
10-26 1万+
今天有兄弟告诉我，测试环境突然AdminServer启动不了了，大家无法测试，查看日志如下：starting weblogic with Java version: Starting WLS with line: /usr/java/jdk1.6.0_29/bin/java -server -Xms2048m -Xmx2048m -Xmn768m -XX:MaxPermSize=512m -X...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值