[
https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675666#action_12675666
]
Alex Boisvert commented on ODE-525:
-----------------------------------
It still doesn't make the information useful nor actionable.
You're saying there's a synchronization issue but you don't provide any detail
on the issue itself. How is the synchronization preventing the system to
achieve better performance? Are there many other threads blocked by this
synchronization?
There's also the fact that these classes are not in Ode itself, they are in 3rd
party libraries... so either there are issues inside these libraries, or how we
use them. It would help to narrow down the issue to one of these two sides.
> 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.
