You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/02/20 19:27:02 UTC

[jira] Commented: (ODE-525) Thread synchronization / block (eg. XML manipulation ) slows ODE down dramaticly

    [ https://issues.apache.org/jira/browse/ODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675427#action_12675427 ] 

Alex Boisvert commented on ODE-525:
-----------------------------------

Sorry, but the data you're providing is not very actionable and probably wrong as well.   (30648 seconds = 510 minutes???  In a 16 minutes test??)

We would need full stacktraces, and use-case that describes what the server is doing and under which circumstances, etc.

> 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.