[
https://issues.apache.org/jira/browse/ODE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maciej Szefler resolved ODE-191.
--------------------------------
Resolution: Fixed
ODE 1.1: Thow qnSubLanguageExecutionFailure fault instead of invalidprocess.
TRUNK: Remove the EvaluationException class, use only FaultException .
> Saxon DynamicError should be reported as BPEL fault
> ---------------------------------------------------
>
> Key: ODE-191
> URL: https://issues.apache.org/jira/browse/ODE-191
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.1
> Reporter: Alex Boisvert
> Fix For: 1.1.1
>
>
> The stacktrace below illustrates a Saxon DynamicError being reported as a
> runtime exception InvalidProcessException.... I think it should be reported
> as a bpel:invalidExpressionValue.
> 09:49:30,731 ERROR [org.apache.ode.bpel.engine.BpelEngineImpl]
> [pool-2-thread-10] Scheduled job failed; jobDetail={type=INVOKE_RESPONSE,
> mexid=4587536, channel=154, iid=4685824}
> java.lang.RuntimeException:
> org.apache.ode.bpel.runtime.InvalidProcessException: Unexpected evaluation
> exception.
> at
> org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:464)
> at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> at
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeContextImpl.java:836)
> at
> org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:365)
> at
> org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:329)
> at
> org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:364)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:316)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:315)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:154)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:314)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:311)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.ode.bpel.runtime.InvalidProcessException: Unexpected
> evaluation exception.
> at org.apache.ode.bpel.runtime.SWITCH.run(SWITCH.java:61)
> at sun.reflect.GeneratedMethodAccessor186.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451)
> ... 15 more
> Caused by: org.apache.ode.bpel.explang.EvaluationException: Error while
> executing an XPath expression: net.sf.saxon.trans.DynamicError: Cannot
> compare xs:string to xs:integer
> at
> org.apache.ode.bpel.elang.xpath20.runtime.XPath20ExpressionRuntime.evaluate(XPath20ExpressionRuntime.java:197)
> at
> org.apache.ode.bpel.elang.xpath20.runtime.XPath20ExpressionRuntime.evaluateAsBoolean(XPath20ExpressionRuntime.java:85)
> at
> org.apache.ode.bpel.runtime.ExpressionLanguageRuntimeRegistry.evaluateAsBoolean(ExpressionLanguageRuntimeRegistry.java:72)
> at org.apache.ode.bpel.runtime.SWITCH.run(SWITCH.java:53)
> ... 19 more
> Caused by: net.sf.saxon.trans.DynamicError: Cannot compare xs:string to
> xs:integer
> at net.sf.saxon.expr.ValueComparison.compare(ValueComparison.java:492)
> at
> net.sf.saxon.expr.ValueComparison.effectiveBooleanValue(ValueComparison.java:442)
> at
> net.sf.saxon.xpath.XPathExpressionImpl.evaluate(XPathExpressionImpl.java:221)
> at
> org.apache.ode.bpel.elang.xpath20.runtime.XPath20ExpressionRuntime.evaluate(XPath20ExpressionRuntime.java:179)
> ... 22 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
