问题描述
我在 WAS 8.5.5 中遇到了一个严重问题.根据我的要求，我已将 xmlparserV2.jar 包含在 JVM 类路径中.我已经重新启动了 WAS，并且服务器开始失败并出现以下错误.我已经取出罐子并进行了测试.没有该条目，服务器工作正常.
I had a severe issue in WAS 8.5.5. I have included the xmlparserV2.jar in JVM classpath as per my requirement. I have restarted the WAS and server start to failed with the follow errors. I have removed the jar and tested. Server is working fine with out that entry.
请告诉我原因以及如何解决.
Please let me know the reason and how can i resolve it.
[3/16/15 6:30:12:406 PDT] 00000001 MBeanDescript W ADMN0001W: The service is unable to parse the MBean descriptor file com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: The service is unable to parse the MBean descriptor file com/ibm/ws/management/descriptor/xml/AdminService.xml.
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:182)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:415)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:190)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:507)
[3/16/15 6:30:12:500 PDT] 00000001 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:Program FilesIBMWebSphereAppServerprofilesAppSrv01logsffdcserver1_b9ae2bfa_15.03.16_06.30.12.4211342510407965994963.txt com.ibm.ws.management.component.AdminImpl.initialize 217
[3/16/15 6:30:12:500 PDT] 00000001 AdminInitiali A ADMN0015I: The administration service is initialized.
[3/16/15 6:30:12:562 PDT] 00000001 MBeanDescript W ADMN0001W: The service is unable to parse the MBean descriptor file com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: The service is unable to parse the MBean descriptor file com/ibm/ws/management/descriptor/xml/ConfigRepository.xml.
at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:182)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:415)
at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:190)
at com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:Program FilesIBMWebSphereAppServerprofilesAppSrv01logsffdcserver1_b9ae2bfa_15.03.16_06.30.12.5627002919638891875819.txt com.ibm.ws.management.repository.FileRepository.initialize 149
[3/16/15 6:30:12:578 PDT] 00000001 FileRepositor E ADMR0006E: An error occurred activating MBean: com.ibm.websphere.management.exception.AdminException: ADMN0005E: The service is unable to activate MBean: type ConfigRepository, collaborator com.ibm.ws.management.repository.FileRepository@df91d010, configuration ID repository, descriptor null.
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:772)
at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:476)
推荐答案
JAR 文件包含一个 META-INFservices 目录，其中包含将覆盖服务器正在使用的 XML 处理器的文件.
The JAR file includes a META-INFservices directory which includes files that will override the XML processors being used by your server.
来自 Java SE javadoc
From Java SE javadoc
如果可用，请使用服务 API(如 JAR 规范中所述)来确定类名.服务 API 将在运行时可用的 jar 中的 META-INF/services/javax.xml.parsers.SAXParserFactory 文件中查找类名.
Use the Services API (as detailed in the JAR specification), if available, to determine the classname. The Services API will look for a classname in the file META-INF/services/javax.xml.parsers.SAXParserFactory in jars available to the runtime.
我使用 7-zip 从 META-INFservices 中删除文件并改用那个 JAR.我的 XML 对象解析现在可以正常工作，其他所有内容均未受影响.
I used 7-zip to delete the files from the META-INFservices and used that JAR instead. My XML Object parsing works now and everything else is un-effected.
这篇关于WAS 8.5.5 中 xmlparserV2.jar 的类路径问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！