首页 > 其他分享 >weblogic乱码报错解决思路

weblogic乱码报错解决思路

时间：2023-09-28 12:36:42浏览次数：46  
标签：java targetserver deploy 乱码 internal weblogic 报错


目录

1.集群备份 weblogic虚拟机快照备份

2.查看主节点控制台面板状态

3.尝试启动程序失败

4.查看162.主节点日志

5.发现程序中乱码

6.修改乱码名称

7.尝试启动，新的报错还是显示乱码

8.修改乱码

9.点击更新程序，继续报错

9.1依然是乱码

10.更新，程序部署路径，换新程序，

11.删除程序，处理程序中的乱码后，重写部署后成功

1.集群备份 weblogic虚拟机快照备份

2.查看主节点控制台面板状态

weblogic乱码报错解决思路_xml

weblogic乱码报错解决思路_XML_02

3.尝试启动程序失败

weblogic乱码报错解决思路_javascript_03

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.主节点日志

weblogic乱码报错解决思路_xml_04

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.发现程序中乱码

weblogic乱码报错解决思路_XML_05

6.修改乱码名称

mv Webة¼þ.html Web组件.html

weblogic乱码报错解决思路_javascript_06

7.尝试启动，新的报错还是显示乱码

weblogic乱码报错解决思路_服务器_07

weblogic乱码报错解决思路_java_08

8.修改乱码

weblogic乱码报错解决思路_java_09

9.点击更新程序，继续报错

weblogic乱码报错解决思路_javascript_10

9.1依然是乱码

weblogic乱码报错解决思路_xml_11

10.更新，程序部署路径，换新程序，

weblogic乱码报错解决思路_xml_12

11.删除程序，处理程序中的乱码后，重写部署后成功

标签：java,targetserver,deploy,乱码,internal,weblogic,报错
From： https://blog.51cto.com/dxbp/7638030

相关文章

  • CentOS 7 显示中文乱码
    1.查看cat /etc/locale.conf LANG=en_US.UTF-82.备份cp /etc/locale.conf /etc/locale.conf_bak3.编辑变量cat> /etc/locale.conf<<EOFLANG="zh_CN.UTF-8"EOFcat> /etc/sysconfig/i18n<<EOFLANG="zh_CN.UTF-8"EOFvi/etc/profile#尾部添加ex......
  • Hydration completed but contains mismatches 报错，如何解决？
    最近在用vue3+node+TS+vite在搭建SSR服务器端渲染项目时候，遇到问题Hydrationcompletedbutcontainsmismatches？字面意思就是客户端激活已完成，但是存在不匹配；若是第一次遇到这个问题，貌似还不是很懂？所谓客户端激活指的是Vue在浏览器端接管由服务器发送的静态HTML,将其变......
  • git 报错Access denied
    remote:[session-614483a1]Accessdeniedfatal:unabletoaccess'https://gitee.com/**/':TherequestedURLreturnederror:403  解决办法： gitconfiguser.name"newname"gitconfigcredential.username"newname"或者删除本地钥匙串......
  • springcloud gateway 获取响应体进行加密操作，byte[]转换String乱码
    记录一下困扰一星期的问题！在全局过滤器中，获取响应体进行加密操作，在拿到byte[]之后转成String，控制台打印出来是乱码，编码也加了UTF-8还是报错。publicMono<Void>filter(ServerWebExchangeexchange,GatewayFilterChainchain){ServerHttpResponseoriginalResponse=ex......
  • SpringBoot启动报错
    问题描述按照以往的代码进行SpringBoot的相应部署，但是爆出来这个错误：问题解决里面说找不到我定义的bean实体类，那就加上这么一条注解，让他能够找到实体类：然后启动：并在浏览器里面查看一下：ok！问题解决！......
  • mojo编程语言：编译后的mojo二进制执行文件调用python库报错——设置MOJO_PYTHON_LIBRAR
    代码：frompythonimportPythonfnf()raises:#ThisisequivalenttoPython's`importnumpyasnp`letnp=Python.import_module("numpy")leta=np.array([1,2,3])print(a)fnmain()raises:f() mojo编译后执行，报错：Moj......
  • Webpack报错Error: error:0308010C:digital envelope routines::unsupported处理
    在学习组件库流程打包的时候报错找不到module，后来改了版本又报错Error:error:0308010C:digitalenveloperoutines::unsupported报错原因：node17+版本对发布的OpenSSL3.0,而OpenSSL3.0对允许算法和密钥大小增加了严格的限制，可能会对生态系统造成一些影响.解决方案：在网上搜索......
  • 编程语言mojo报错：error: cannot call function that may raise in a context that can
    代码：frompythonimportPythonfnmain():#fnmain()raises:#ThisisequivalenttoPython's`importnumpyasnp`letnp=Python.import_module("numpy")leta=np.array([1,2,3])print(a) 运行报错：[02:19:48](mojo)dev......
  • 导入mysql文件报错
    mysql报错：「ERR」1273-Unknowncollation:'utf8mb4_0900_ai_ci'专注数据库知识分享2022-09-2719:05甘肃#MySQL专栏#mysql导入sql文件报错：[ERR]1273-Unknowncollation:'utf8mb4_0900_ai_ci'大致原因：sql对应的mysql版本高于当前要导入的mysql库的版本，引发......
  • java程序，如何打印详细报错堆栈信息
    try{System.out.println(1/0);}catch(finalExceptione){log.error("ERROR","Errorfound:",e);log.error("ERROR","Errorfound:"+e.getMessage());log.error("ERROR","Errorfo......

赞助商

阅读排行

网站主页关于我们联系我们网站地图

本网站内容转载自其他媒体，侵权联系[admin##ips99.com]。

Copyright © 2020-2023 IPS99 版权所有 IPS99