Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 658
  • Last Modified:

org/apache/xalan/xpath/xdom/XercesLiaison, method: parse signature error

Hi,
Our application use Websphere 5.1.2, JSP 1.2, Struts, XML ,XSL and itext. Application use Xalan and Xerces(1.4.4) parsers to format XML at run time. It runs into following error. I googled on it and found some solution on Sun web site for Sun One application server (solution was specific to class loading mechnism application server has) but I can't find any solution in WebSphere environment.  Any one has any idea?
Thanks.

[4/7/06 13:16:37:164 EDT] 61afca87 WebGroup      E SRVE0026E: [Servlet Error]-[(class: org/apache/xalan/xpath/xdom/XercesLiaison, method: parse signature: (Lorg/xml/sax/InputSource&#59;)V) Incompatible object argument for method call]: java.lang.VerifyError: (class: org/apache/xalan/xpath/xdom/XercesLiaison, method: parse signature: (Lorg/xml/sax/InputSource;)V) Incompatible object argument for method call
      at java.lang.Class.forName1(Native Method)
      at java.lang.Class.forName(Class.java(Compiled Code))
      at org.apache.xalan.xslt.XSLTEngineImpl.<init>(XSLTEngineImpl.java:360)
      at org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(XSLTProcessorFactory.java:79)
      at gov.ssa.oassis.ssi.erz.l732.QuestionTxtFileManager.sApplyXSL(QuestionTxtFileManager.java:285)
      at gov.ssa.oassis.ssi.erz.l732.QuestionTxtFileManager.createTxtFile(QuestionTxtFileManager.java:191)
      at gov.ssa.oassis.ssi.erz.l732.QuestionPDFScheduler.QuestionPDFCreate(QuestionPDFScheduler.java:66)
      at gov.ssa.oassis.ssi.erz.L732.action.PdfViewServletAction.execute(PdfViewServletAction.java:47)
      at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
      at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
      at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
      at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
      at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
      at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:76)
      at gov.ssa.framework.security.SecurityFilter.doFilter(SecurityFilter.java:99)
      at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:132)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:71)
      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
      at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
      at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
      at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
      at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
      at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
      at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
      at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
      at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
0
akashpan1
Asked:
akashpan1
1 Solution
 
avinthmCommented:
Try a different version of xalan jar file. I am not sure whether its a version problem, but u can give it a try.
One more thing. What is your WAS installed path ? There can be a problem if there is any space in your classpath.
like "C:\Program Files\IBM\...." (the space in Progam Files)

0
 
stratorCommented:
Hi akashpan1,

the xml-parsers used by websphere application server are often older than the one
you may use in your application.
As websphere uses the PARENT_FIRST policy for classloaders (according to the j2ee spec),
the libraries from websphere are searched after classes before libraries within the ear/ejb/war.
So if the method signature of a class has changed from the version used by websphere to the
version used within your application, this will result in the exceptions you described.
As a quick solution just change the classloader policy from PARENT_FIRST to PARENT_LAST during
the deployment. But be carefull - this might result in other unexpected side effects.

Bye,
Torsten
0
 
avinthmCommented:
Hi akashpan1,

can u tell us what was the problem ? And why C grade to the answer?

cheers
0
 
akashpan1Author Commented:
The xalan jar file is at the same place where we have other jar files. We don't get any problem with those. Another thing is we run application directly from the websphere so I don't think we have spacing issue.
0
 
jkmyoungCommented:
In your xslt file, do you call any java extensions?
I could see you getting that error if you passed in the wrong type of argument to an extension. eg passing in an integer to a function that expects a node-set.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now