weblogic server deployment -stage mode

本文深入解析了在部署多个WebLogic Server实例时,如何选择Stagemode、Nostagemode与External_stagemode三种部署模式。重点介绍了每种模式的工作原理、适用场景以及对应用部署的影响,帮助开发者根据实际情况灵活选择最合适的部署方式。

- Stage mode—The Administration Server copies the archive files from their source location to a location on each of the targeted Managed Servers that deploy the archive. For example, if you deploy a J2EE Application to three servers in a cluster, the Administration Server copies the application archive files to each of the three servers. Each server then deploys the J2EE Application using its local copy of the archive files. 
Stage mode is the default mode when deploying to more than one WebLogic Server instance. 

- Nostage mode—The Administration Server does not copy the archive files from their source location. Instead, each targeted server must access the archive files from a single source directory for deployment. For example, if you deploy a J2EE Application to three servers in a cluster, each server must be able to access the same application archive files (from a shared or network-mounted directory) to deploy the application. 
Nostage mode is the default mode when deploying only to the Administration Server (for example, in a single-server domain). You can also select nostage mode if you run a cluster of server instances on the same machine. 

- External_stage mode—External_stage mode is similar to stage mode, in that the deployment files must reside locally to each targeted server. However, the Administration Server does not automatically copy the deployment files to targeted servers in external_stage mode; instead, you must manually copy the files, or use a third-party application to copy the files for you. 

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
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值