You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Matthieu Riou (JIRA)" <ji...@apache.org> on 2008/06/25 17:42:45 UTC

[jira] Resolved: (ODE-314) Incorrect exception reported when exception is issued in DoXslTransform

     [ https://issues.apache.org/jira/browse/ODE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthieu Riou resolved ODE-314.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2
         Assignee: Matthieu Riou

That should be fixed in our repository now.

> Incorrect exception reported when exception is issued in DoXslTransform
> -----------------------------------------------------------------------
>
>                 Key: ODE-314
>                 URL: https://issues.apache.org/jira/browse/ODE-314
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>            Reporter: Alexey Ousov
>            Assignee: Matthieu Riou
>            Priority: Minor
>             Fix For: 1.2
>
>
> When some exception occur in DoXslTransform (say NullPointerException), incorrect exception is reported in debug logs instead of it (supposely because of trying to call org.jaxen.FunctionCallException.initCause(e)):
> ERROR - JacobVPU$JacobThreadImpl.run(463) | Method "run" in class "org.apache.ode.bpel.runtime.ASSIGN" threw an unexpected exception.
> java.lang.IllegalStateException: Cause cannot be reset
> 	at org.jaxen.saxpath.SAXPathException.initCause(SAXPathException.java:137)
> 	at org.apache.ode.bpel.elang.xpath10.runtime.WrappedFaultException$JaxenFunctionException.<init>(WrappedFaultException.java:63)
> 	at org.apache.ode.bpel.elang.xpath10.runtime.JaxenContexts$DoXslTransformFunction.call(JaxenContexts.java:371)
> 	at org.jaxen.expr.DefaultFunctionCallExpr.evaluate(DefaultFunctionCallExpr.java:177)
> 	at org.jaxen.expr.DefaultXPathExpr.asList(DefaultXPathExpr.java:102)
> 	at org.jaxen.BaseXPath.selectNodesForContext(BaseXPath.java:674)
> 	at org.jaxen.BaseXPath.selectNodes(BaseXPath.java:213)
> 	at org.apache.ode.bpel.elang.xpath10.runtime.XPath10ExpressionRuntime.evaluate(XPath10ExpressionRuntime.java:103)
> 	at org.apache.ode.bpel.runtime.ExpressionLanguageRuntimeRegistry.evaluate(ExpressionLanguageRuntimeRegistry.java:80)
> 	at org.apache.ode.bpel.runtime.ASSIGN.evalRValue(ASSIGN.java:196)
> 	at org.apache.ode.bpel.runtime.ASSIGN.copy(ASSIGN.java:348)
> 	at org.apache.ode.bpel.runtime.ASSIGN.run(ASSIGN.java:81)
> 	at sun.reflect.GeneratedMethodAccessor64.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)
> 	at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> 	at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeContextImpl.java:833)
> 	at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:402)
> 	at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:326)
> 	at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> 	at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:337)
> 	at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:336)
> 	at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
> 	at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:335)
> 	at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:332)
> 	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)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.