[
https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759062#action_12759062
]
Mateusz Nowakowski commented on ODE-525:
----------------------------------------
I've found the same during JProfiling and YourKit profiling.
I've profiled ODE inside ServiceMix (Fuse to be more precise)
and saw that the ODE threads are blocked most of the time on
net.sf.saxon.om.NamePool monitor.
I can't provide you precise data, but about 90% blocked time was on this
monitor on both Java profilers.
The issue is that how Saxon is used in ODE.
ODE 1.2 uses Saxon in 8.7 version and I googled that it is possible to provide
new NamePool object to each xPath evaluation. This causes that threads are no
longer blocked on this monitor.
Hovewer the issue may be solved inside Saxon library in 9.x, but I haven't
tested it yet, because there are no working ServiceMix ODE 1.3.x release.
I'll try to find time to test it against 1.3.4-SNAPSHOT and figure it out if
the issue still occurs.
> Thread synchronization / block (eg. XML manipulation ) slows ODE down
> dramaticly
> --------------------------------------------------------------------------------
>
> Key: ODE-525
> URL: https://issues.apache.org/jira/browse/ODE-525
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: ODE 1.2
> JAVA 5.0+
> Reporter: Shammy Chen
>
> Recently we've been profiling ODE by jProfiler and found thread
> synchronization block ODE and AXIS2 threads so much.
> For example,in our 16 minutes test,calss sun.misc.URLClassPath blocked 342282
> times and amounted to 30648 seconds. Class net.sf.saxon.om.NamePool has
> similar problem, maybe there are other candidates.
> I think, if we resolve thread synchronization problem, ODE can perform much
> better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
