[
https://issues.apache.org/jira/browse/ODE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698958#action_12698958
]
Karthick Sankarachary commented on ODE-575:
-------------------------------------------
Ciaran,
Thanks for bringing this issue to our attention. The solution you proposed
looks good, in general. However, I suggest that we make one minor change to
your patch. Instead of swallowing the exception thrown in
OAssign.Literal.getXMLLiteral(), I would rather just throw it, so that it
causes a selection failure in the Assign statement. I believe that would be the
behavior the user might expect to see if there was indeed something fishy about
the XML literal. WDYT?
Regards,
Karthick
> oAssign$Literal seems to consume an excessive volume of memory
> --------------------------------------------------------------
>
> Key: ODE-575
> URL: https://issues.apache.org/jira/browse/ODE-575
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Environment: n/a
> Reporter: Ciaran Jessup
> Attachments: AssignLiteralMemoryRedux.patch,
> reduce-xml-literal-size.patch
>
>
> Our BPEL workflows contain a large number of literal assigns, these are
> stored as Document instances in the BPEL runtime, which are cloned each time
> they are referenced, this appears to consume an immense amount of memory :(
> making it un-workable for my current BPEL flows :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
