Radim Kolarik wrote:
Hi,
We are experiencing a problem on Websphere 6.1.0.11 with Tuscany 1.0.
When we set all classloader properties, as mentioned before,
I'm assuming that you mean: change classloader properties of your Webapp
to parent-last / single, correct?
we are
getting the following exception when we try to call Websphere's
AdminService.getAttribute:
Stack Dump = java.lang.ClassCastException:
org.apache.xerces.jaxp.SAXParserFactoryImpl incompatible with
javax.xml.parsers.SAXParserFactory
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.makeParser(XMLLoadImpl.java:299)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:140)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:179)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.basicDoLoad(CompatibilityXMIResourceImpl.java:180)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.doLoad(CompatibilityXMIResourceImpl.java:173)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1094)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:900)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.load(CompatibilityXMIResourceImpl.java:259)
at
com.ibm.websphere.resource.WASResourceImpl.load(WASResourceImpl.java:61)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:249)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:264)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:390)
at
com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:158)
at
com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:143)
at
com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:325)
at
com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:298)
at
com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:274)
at
com.ibm.ws.runtime.component.EndPointMgrImpl.getNodeHostName(EndPointMgrImpl.java:488)
at
com.ibm.ws.management.AdminHelperImpl.getNodeHostName(AdminHelperImpl.java:116)
at
com.ibm.ws.management.component.JVMMBean.getJVMNode(JVMMBean.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at
javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089)
at
javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971)
at
javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1373)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:114)
at
com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:199)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:656)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:677)
at
com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminServiceImpl.java:687)
at com.company.websphere.WebSphereServerHelper.initialise(Unknown
Source)
.....
It is really strange, because
org.apache.xerces.jaxp.SAXParserFactoryImpl is derived from
SAXParserFactory as far as I know.
Can you give me a little more context?
Are you calling AdminService.getAttribute() from your Webapp or are you
running into this issue when starting the server, independent of the Webapp?
Can you show me the complete stack trace from the log or the FFDC
created when you get the exception... usually the answer to all stack
traces lies in the .... part :)
Does anybody have an idea what could be causing the problem?
Probably but it'll depend on your answer to my above questions :)
Thanks,
Radim
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
