目录
1.集群备份 weblogic虚拟机快照备份
2.查看主节点控制台面板状态
3.尝试启动程序失败
4.查看162.主节点日志
5.发现程序中乱码
6.修改乱码名称
7.尝试启动，新的报错还是显示乱码
8.修改乱码
9.点击更新程序，继续报错
9.1依然是乱码
10.更新，程序部署路径，换新程序，
11.删除程序，处理程序中的乱码后，重写部署后成功
1.集群备份 weblogic虚拟机快照备份
2.查看主节点控制台面板状态
3.尝试启动程序失败
weblogic.management.DeploymentException: [J2EE:160177]The application at "/home/weblogic/user_projects/domains/zsasdz/servers/Sexxer-0/stage/fxxxbi/finebi" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, consult the WebLogic Server documentation.4.查看162.主节点日志
DOMAIN] > <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException: [J2EE:160177]The application at "/home/webloxxzgic/wlsInstall/user_projects/domains/zz/servers/Server-0/stage/fxnxxxxebi/fxxi" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, consult the WebLogic Server documentation.
at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:188)
at weblogic.application.internal.DeploymentManagerImpl.access$800(DeploymentManagerImpl.java:61)
at weblogic.application.internal.DeploymentManagerImpl$DeploymentCreatorImpl.createDeployment(DeploymentManagerImpl.java:628)
at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:240)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:223)
at weblogic.deploy.internal.targetserver.operations.StartOperation.createAndPrepareContainer(StartOperation.java:95)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doPrepare(StartOperation.java:108)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:242)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:800)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1352)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:270)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:177)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:186)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:14)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:681)
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)
>
####<2022-11-10 上午08时51分16,626秒 CST> <Warning> <netuix> <jytjqgl02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <102cdd81-dca9-41cf-9ce4-69f0e0be6350-0000007e> <1668041476626> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-423420> <开始操作或刷新操作时执行重定向。重定向 url 为 /console/console.portal?_nfpb=true&_pageLabel=AppDeploymentsRuntimePage。>
####<2022-11-10 上午08时51分52,647秒 CST> <Info> <Health> <jytjqgl02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <102cdd81-dca9-41cf-9ce4-69f0e0be6350-00000015> <1668041512647> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-310002> <54% of the total memory in the server is free.>
####<2022-11-10 上午08时52分12,098秒 CST> <Info> <WorkManager> <jytjqgl02> <AdminServer> <Timer-2> <<WLS Kernel>> <> <102cdd81-dca9-41cf-9ce4-69f0e0be6350-00000009> <1668041532098> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-002959> <Self-tuning thread pool contains 0 running threads, 1 idle threads, and 14 standby threads>
5.发现程序中乱码
6.修改乱码名称
mv Webة¼þ.html Web组件.html
7.尝试启动，新的报错还是显示乱码
8.修改乱码
9.点击更新程序，继续报错
9.1依然是乱码
10.更新，程序部署路径，换新程序，
