java - Classpath Issue with xmlparserV2.jar in WAS 8.5.5 -

I was 8.5.5 in a serious issue. According to my need, I failed to follow the restart covers xmlparserV2.jar in the JMM Kcshapth I WAS server errors. I removed the jar and tested it. The server is working fine with that entry

Please tell me the reason and how can I solve it

 . [16/03/15 6: 30: 12: 406 PDT] 00000001 MBeanDescript W ADMN0001W: service MBean descriptor file is unable to parse com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: service MBean descriptor file com / IBM Unable to parse / ws / management / narrator / xml / AdminService.xml On com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile (MBeanDescriptorManager.java:415) (MBeanDescriptorLoader.java:182) on com.ibm.ws.management on .descriptor.MBeanDescriptorManager.getDescriptor com.ibm.ws.management.MBeanFactoryImpl.activateMBean (MBeanDescriptorManager.java:190) (MBeanFactoryImpl.java:507) [3/16/15 6: 30: 12: 500 PDT] 00000001 FfdcProvider W Com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: C: \ Program Files \ IBM \ WebSphere \ AppServer \ profiles \ AppSrv01 \ logs \ ffdc \ server1_b9ae2bfa_15.03.16_06.30.12.4211342510407965994963.txt emproved FFDC event. ibm.ws.management.component.AdminImpl.initialize 217 [3/16/15 6: 30: 12: 500 PDT] 00000001 AdminInitiali a ADMN0015I: Administration service is not started. [16/03/15 6: 30: 12: 562 PDT] 00000001 MBeanDescript W ADMN0001W: ADMN0001W: Unable to parse service is MBean descriptor file is unable to parse com.ibm.websphere.management.exception.DescriptorParseException MBN descriptor File Comm / IBM / WS / Management / Descriptor / XML / Conflict Repository.exml com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile (MBeanDescriptorManager.java:415) at (MBeanDescriptorLoader.java:182) .descriptor.MBeanDescriptorManager.getDescriptor on com.ibm.ws.management (MBeanDescri ptorManager.java:190) on com.ibm.ws.ffdc.impl.FfdcProvider log Inkent FFDC1003I: Ffdisi event emitted at C: \ Program Files \ IBM \ web \ AppServer \ profiles \ AppSrv01 \ logs \ ffdc \ com.ibm. ws.management.repository.FileRepository.initialize 149 server1_b9ae2bfa_15.03.16_06.30.12.5627002919638891875819.txt [3/16/15 6: 30: 12: 578 PDT] 00000001 FileRepositor e ADMR0006E: an error occurred activating MBean: com.ibm .websphere.management.exception.AdminException: ADMN0005E: type ConfigRepository, associate com.ibm.ws.management.repository.FileRepository@df91d010, configuration ID stores descriptor null service MBean is unable to activate. com.ibm.ws.management.MBeanFactoryImpl.activateMBean (MBeanFactoryImpl.java:772) on com.ibm.ws.management.MBeanFactoryImpl.activateMBean (MBeanFactoryImpl.java:476)  

on

Text after "

Has this problem been resolved?

Because I have to face the same kind of issue. Getting the first - java.sql.SQLException: java.lang.NoClassDefFoundError: oracle.xml.parser.v2.XMLParseException To fix this problem if we add xmlparserv2.jar to the JDBC square path if the application is running fine but my JVM was Crush (coil login no disturbances) has been removed from the Classpath this jar server behaves properly.