[ 
https://issues.apache.org/jira/browse/UIMA-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555067#comment-15555067
 ] 

Marshall Schor commented on UIMA-5126:
--------------------------------------

Looking at the stack trace, the last UIMA code is a call in 
org.apache.uima.util.XMLSerializer, line 277, which is 
{code}mHandler.startElement(...){code}
mHandler is set from 
javax.xml.transform.sax,SAXTransformerFactory.newInstance().

Looks like Saxon 9 registered itself as the transformer factory.

An internet search for a saxon 9 bug of this variety did not turn up anything.

Burn, if you could reliably reproduce this, could you wrap the call on line 277 
of XMLSerializer with a try / catch, and when the error happens, print out the 
arguments?  Perhaps UIMA is passing flaky (that's a technical term :-) ) 
arguments to start element.

> UIMA-AS thows an NPE if saxon9he.jar is in the classpath
> --------------------------------------------------------
>
>                 Key: UIMA-5126
>                 URL: https://issues.apache.org/jira/browse/UIMA-5126
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>            Priority: Minor
>             Fix For: 2.9.0AS
>
>
> Works OK if saxon8 is in the classpath.  Failure occurs when replying to a 
> getmeta request.  The stack trace is in UIMA-5117



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to