Saxon Exception
Replies (3)
Please register to reply
RE: Saxon Exception
-
Added by Anonymous over 16 years ago
Legacy ID: #4716679 Legacy Poster: Michael Kay (mhkay)
This symptom used to crop up from time to time - it was generally caused by corruption of the expression tree during rewrites by the optimizer - nothing to do with threading issues. I haven't seen the problem for some time, so I'd advise moving to a more recent release. The current release 9.0.0.2 is proving pretty stable.
RE: Saxon Exception
-
Added by Anonymous over 16 years ago
Legacy ID: #4725267 Legacy Poster: jbeuree (jbeuree)
I work with bkbateman above and have tried using the latest release (9.0.0.2) and it gives a similar problem: java.lang.AssertionError: Value of variable is undefined (null) Variable vs a t 550 of resource://xqueries/vl.xq Variable vs2 at 627 of resource://xqueries/vl.xq Variable distinctvs at 629 of resource://xqueries/vl.xq at net.sf.saxon.expr.VariableReference.iterate(VariableReference.java:40 4) at net.sf.saxon.functions.Aggregate.evaluateItem(Aggregate.java:96) at net.sf.saxon.expr.ValueComparison.effectiveBooleanValue(ValueComparis on.java:552) at net.sf.saxon.instruct.Choose.iterate(Choose.java:687) at net.sf.saxon.expr.LetExpression.iterate(LetExpression.java:308) at net.sf.saxon.value.Closure.iterate(Closure.java:181) at net.sf.saxon.value.Value.getIterator(Value.java:216) at net.sf.saxon.expr.UserFunctionCall.iterate(UserFunctionCall.java:369) at net.sf.saxon.instruct.BlockIterator.next(BlockIterator.java:42) at net.sf.saxon.value.MemoClosure$ProgressiveIterator.next(MemoClosure.j ava:327) at net.sf.saxon.functions.Existence.effectiveBooleanValue(Existence.java :109) at net.sf.saxon.expr.BooleanExpression.effectiveBooleanValue(BooleanExpr ession.java:181) at net.sf.saxon.instruct.Choose.processLeavingTail(Choose.java:618) at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:399) at net.sf.saxon.instruct.Instruction.process(Instruction.java:94) at net.sf.saxon.expr.LetExpression.process(LetExpression.java:380) at net.sf.saxon.instruct.UserFunction.process(UserFunction.java:347) at net.sf.saxon.expr.UserFunctionCall.process(UserFunctionCall.java:417) at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:401) at net.sf.saxon.instruct.Instruction.process(Instruction.java:94) at net.sf.saxon.instruct.ElementCreator.constructElement(ElementCreator. java:378) at net.sf.saxon.instruct.ElementCreator.evaluateItem(ElementCreator.java :324) at net.sf.saxon.instruct.Instruction.iterate(Instruction.java:309) at net.sf.saxon.instruct.BlockIterator.next(BlockIterator.java:42) at net.sf.saxon.query.XQueryExpression$ErrorReportingIterator.next(XQuer yExpression.java:822) at net.sf.saxon.query.QueryResult.serializeSequence(QueryResult.java:187 ) at net.sf.saxon.query.QueryResult.serializeSequence(QueryResult.java:133 ) ... Basically, in this scenario, the first variable listed should not match anything and should be an empty sequence. This will cause the others to be empty. Instead, this error sometimes happens. It doesn't look like an internal bug rather than something caused by bad or incorrect xquery code.
RE: Saxon Exception
-
Added by Anonymous over 16 years ago
Legacy ID: #4725285 Legacy Poster: Michael Kay (mhkay)
Definitely a Saxon bug then. Could you let me have the code that causes it please?
Please register to reply
.