I would like to know whether anyone has come across the following error trace. Could someone please suggest a solution for the same. We have been stuck up with this issue for quite sometime now. What is even more frustrating is that the code seems to be working perfectly allright on our local development workspace (Web Sphere Application Developer 4.0.1). However when the code is deployed on the Web Sphere Application Server (4.0) we get this error. Is this some error with the code or is something to do with the servers it is being deployed on.Any Suggestions?
Thanks in Advance. Any Help would be really appreciated.
Regards, Sunoo
[7/27/05 18:49:32:761 SGT] 4f1541 WebGroup X Servlet Error: : java.lang.ExceptionInInitializerError: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:147) at org.apache.soap.util.xml.XMLParserUtils.refreshDocumentBuilderFactory(Unknown Source) at org.apache.soap.util.xml.XMLParserUtils.<clinit>(Unknown Source) at org.apache.soap.rpc.Call.invoke(Unknown Source) at com.ford.pms.externalinterface.outbound.utils.SOAPOutboundTransportHandler.processOutbound(SOAPOutboundTransportHandler.java:67) at com.ford.pms.externalinterface.outbound.handler.RequestResponseHandler.sendRequest(RequestResponseHandler.java:67) at com.ford.pms.externalinterface.outbound.handler.PartsAvailabilityHandler.process(PartsAvailabilityHandler.java:42) at com.ford.pms.externalinterface.outbound.handler.RequestResponseHandler.processRequest(RequestResponseHandler.java:36) at com.ford.pms.externalinterface.outbound.utils.RequestResponseManager.process(RequestResponseManager.java:118) at com.ford.pms.parts.struts.PartsOrderAction.perform(PartsOrderAction.java:1436) at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586) at com.cts.yardelligent.utils.YardelligentServlet.process(YardelligentServlet.java:208) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167) at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110) at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472) at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012) at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:721) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:374) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:118) at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134) at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239) at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67) at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106) at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:154) at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:317) at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:391) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:284) at com.ibm.ws.util.CachedThread.run(ThreadPool.java:144)
Praveena Venigalla
Ranch Hand
Joined: Oct 29, 2003
Posts: 36
posted
0
Hi, I think some Jar files are missing,when you are deploying in the Websphere App Server 4.0 . If you can verify your classpath on your local machine to that of the other Env where you are deploying ,then you may come up with solution.
Thanks, Praveena
Praveena Venigalla<br />OCP,SCJP,SCWCD,SCBCD<br />--Knowledge is attained by learning to hold one's tongue
Tim West
Ranch Hand
Joined: Mar 15, 2004
Posts: 539
posted
0
Doesn't look like they are missing per se to me, rather, it looks like JAXP has been set to use a library other than Xerces - maybe Crimson, or an IBM parser.
In an ideal world you wouldn't need to use Xerces - you'd just use the JAXP APIs. But that would mean code modification...I don't know whether that's practical for you.
Assuming it's not, you'll need to set up JAXP to use Xerces rather than whatever it's using now. To do this, you need to set two global properties:
You can do this by passing -D properties to the java command used to start Websphere (though who knows, maybe that'll break Websphere...). Another way you can set them is by putting them in a file called 'jaxp.properties' in JAVA_HOME/lib.
-Tim
Sunoo Varghese
Greenhorn
Joined: Sep 11, 2004
Posts: 19
posted
0
Tim & Praveena,
Thanks a lot guys. Would try implementing your suggestions and get back.
0
